We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To not expand on the number of custom header parsers in HTTP libraries, all new headers must follow https://tools.ietf.org/html/draft-ietf-httpbis-header-structure. This is already de facto enforced, but it would be good to have it documented.
cc @mnot (feel free to unsubscribe, but I thought you might want to know)
The text was updated successfully, but these errors were encountered:
If we resolve to work on this, I wonder if this means we should add a new section for HTTP-related principles?
Sorry, something went wrong.
https://w3ctag.github.io/design-principles/#new-http-header-syntax
Discussing today and we think we can close this.
ylafon
No branches or pull requests
To not expand on the number of custom header parsers in HTTP libraries, all new headers must follow https://tools.ietf.org/html/draft-ietf-httpbis-header-structure. This is already de facto enforced, but it would be good to have it documented.
cc @mnot (feel free to unsubscribe, but I thought you might want to know)
The text was updated successfully, but these errors were encountered: