Skip to content
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.

Sign up for GitHub

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

Jump to bottom

RFC 7231 content-type charset param case sensitivity #13

Closed
reschke opened this issue May 4, 2016 · 2 comments
Closed

RFC 7231 content-type charset param case sensitivity #13

reschke opened this issue May 4, 2016 · 2 comments
Labels
editorial semantics

Comments

@reschke
Copy link
Contributor

reschke commented May 4, 2016 •
edited

https://greenbytes.de/tech/webdav/rfc7231.html#media.type

The type, subtype, and parameter name tokens are case-insensitive. Parameter values might or might not be case-sensitive, depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing of a media-type, depending on its definition within the media type registry.

...it then continues showing examples that imply that the charset value is case-insensitive (which is correct), but it would be helpful if it cited RFC 2046 which defines charset's case sensitivity.
@mnot mnot added the semantics label Jun 20, 2017
@mnot mnot added the editorial label Jun 29, 2018
@royfielding
Copy link
Member

We define charset in the next section, which already references the normative specs (that displaced RFC 2046 as the formal definition).

@reschke
Copy link
Contributor Author

reschke commented Oct 11, 2018

See #113

royfielding added a commit that referenced this issue Mar 8, 2019
@royfielding
Merge pull request #113 from httpwg/reschke-i13
12c2576 
Clarify that the charset parameter value is case-insensitive due to the definition in RFC 2046 (closes #13)
reschke added a commit that referenced this issue Mar 9, 2019
@reschke
sort change log for #13, regen HTML
07c4f24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
editorial semantics
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mnot @reschke @royfielding