-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
HTTP headers index #7355
Labels
clarification
Standard could be clearer
Comments
annevk
added a commit
that referenced
this issue
Nov 23, 2021
This concludes moving away from using IANA templates to define HTTP headers. It takes care of Last-Event-ID, Ping-From, Ping-To, Refresh, and X-Frame-Options. It also adds an index to ensure these headers are still easy to find. And finally it corrects the casing of several index sections. This helps with #7274 (kept open to update the IANA registry) and fixes #7355.
annevk
added a commit
that referenced
this issue
Nov 24, 2021
This concludes moving away from using IANA templates to define HTTP headers. It takes care of Last-Event-ID, Ping-From, Ping-To, Refresh, and X-Frame-Options. It also adds an index to ensure these headers are still easy to find. And finally it corrects the casing of several index sections. This helps with #7274 (kept open to update the IANA registry) and fixes #7355.
mfreed7
pushed a commit
to mfreed7/html
that referenced
this issue
Jun 3, 2022
This concludes moving away from using IANA templates to define HTTP headers. It takes care of Last-Event-ID, Ping-From, Ping-To, Refresh, and X-Frame-Options. It also adds an index to ensure these headers are still easy to find. And finally it corrects the casing of several index sections. This helps with whatwg#7274 (kept open to update the IANA registry) and fixes whatwg#7355.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a follow-up to #7274, should we add an index for HTTP headers the HTML specification defines? This seems somewhat useful. The MIME types index is apparently all MIME types the specification mentions, but does an HTTP headers index have to be consistent with that or is it fine if it lists introduced HTTP headers instead?
The text was updated successfully, but these errors were encountered: