-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make clear that names/values are UTF-8 in x-www-form-urlencoded #235
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't it make sense to introduce the general encoding scheme somewhere in terminology with most of the original text you linked and then reference to it?
MUST be encoded using the UTF-8 character encoding scheme [RFC3629] first; the resulting octet sequence then needs to be further encoded using the escaping rules defined in [W3C.REC-html401-19991224].
Thanks Christian. I'm not sure if I want to start picking at some of that as things start to unravel/get more complicated. The RFC6749 definition isn't actually the canonical one anymore - the definition of |
In general I would just remove the word |
I tend to agree with @nemqe 's suggetion to remove |
As per feedback on PR. Co-authored-by: Kristina <[email protected]>
Thanks for the feedback, and to Kristina for adding the suggestions - I've committed them, please review/approve! |
Mirrors text used in https://datatracker.ietf.org/doc/html/rfc6749#appendix-B
closes #40