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
See https://www.rfc-editor.org/errata/eid4689
The text was updated successfully, but these errors were encountered:
We currently use "token", but this includes characters not allowed by RFC 2978 (as corrected by https://www.rfc-editor.org/errata/eid1912).
Options:
In https://www.rfc-editor.org/errata/eid4689 it was proposed to use RFC 5987, but that would introduce a normative reference that we do not want here.
Sorry, something went wrong.
Actually:
RFC2616.token: "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "." / DIGIT / ALPHA / "^" / "_" / "`" / "|" / "~" RFC2978.mimecharset: "!" / "#" / "%" / "&" / "+" / "-" / DIGIT / ALPHA / "^" / "_" / "`" / "{" / "}" / "~" Rfc2616.token - Rfc2978.mimecharsetWithErratum: "$" / "'" / "*" / "." / "|" Rfc2978.mimecharsetWithErratum - Rfc2616.token: "{" / "}"
where RFC2978.mimecharset has the erratum 1912 applied...
So in theory "{" and "}" could appear in charset names, but are not allowed in tokens. In practice, no such charset is registered.
I'm tempted to open another erratum against 2978. Feedback appreciated.
https://www.rfc-editor.org/errata/eid5433
See #130
httpwg/http-core@3675392
refine text for resolution oissue #100
b6f1739
reschke
No branches or pull requests
See https://www.rfc-editor.org/errata/eid4689
The text was updated successfully, but these errors were encountered: