You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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 fixeswhatwg#7355.
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: