NOTE: The current preferred location for bug reports is the GitHub issue tracker.
First Last Prev Next    This bug is not in your last search results.
Bug 933 - Make ContentTypeParser a more useful, error-reporting parser
Make ContentTypeParser a more useful, error-reporting parser
Status: RESOLVED FIXED
Product: Validator.nu
Classification: Unclassified
Component: Non-schema checkers
HEAD
All All
: P2 normal
Assigned To: Michael[tm] Smith
http://greenbytes.de/tech/tc/httpcont...
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-07-19 08:45 CEST by Michael[tm] Smith
Modified: 2012-07-30 17:31 CEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael[tm] Smith 2012-07-19 08:45:28 CEST 
RFC 2616 does not allow  white space around the "=" sign in parameters, and most browsers ignore the value of the charset parameter if is has white space around the "=" sign.

Test case here:

http://greenbytes.de/tech/tc/httpcontenttype/#textplainutf8ws

Results here:

http://greenbytes.de/tech/tc/httpcontenttype/textplainutf8ws.asis

Excerpt from the part of RFC 2616 that states the requirement:

http://tools.ietf.org/html/rfc2616#section-3.7
"Linear white space (LWS) MUST NOT be used between the type and subtype, nor between an attribute and its value."
Comment 1 Michael[tm] Smith 2012-07-30 16:10:06 CEST 
Repurposing this bug for recording changes made to turn ContentTypeParser a more useful, error-reporting parser.
First Last Prev Next    This bug is not in your last search results.