-
Notifications
You must be signed in to change notification settings - Fork 43
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
MIME type parsing #33
Comments
One of the things that I couldn't find addressed anywhere is something like |
See also whatwg/mimesniff#30 e.g., discussion of multiple content-types. This has potential security impact. |
For MIME types I ended up (re)writing https://mimesniff.spec.whatwg.org/#understanding-mime-types btw and also have a bunch of tests at https://github.com/w3c/web-platform-tests/tree/master/mimesniff/mime-types. |
Discussed in Basel; inclination is to change the ABNF, and survey similar places to align if necessary. |
@mnot pardon my ignorance but what is ABNF? Am I wrong to assume it is this ? Thanks in advance! |
It is. |
Note that this is about the trailing semicolon, at least initially. |
Discussed on editors' call; we should create a new ABNF rule |
Just to check (grep in httpbis.abnf):
So "expectation" needs a fix (see #420). So "Expect" would be the only affected field in addition to "Content-Type". (Because "TE" is special). Are we ok with that? That said, do we want:
or
? |
See #427 (comment) |
See http://www.rfc-editor.org/errata_search.php?rfc=7231&eid=4031 (rejected due to scope). Clients typically (or all?) allow
text/html;
despite it being invalid.The text was updated successfully, but these errors were encountered: