A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Talk:PragmaExtensions: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Theimp: No, it's not. Anyone is as free to propose additions to the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Permanent Message Header Field Registry, as they are to edit this wiki. Document it there first, as required by the <abbr title="Hypertext Markup Language">HTML</abbr> <abbr title="specification">spec.</abbr> By all means, please document everything — but follow the standards process and begin at the beginning; not at the end. | Theimp: No, it's not. Anyone is as free to propose additions to the <abbr title="Internet Assigned Numbers Authority">IANA</abbr> Permanent Message Header Field Registry, as they are to edit this wiki. Document it there first, as required by the <abbr title="Hypertext Markup Language">HTML</abbr> <abbr title="specification">spec.</abbr> By all means, please document everything — but follow the standards process and begin at the beginning; not at the end. | ||
Hixie: No. The goal is to document reality. Reality is that these fields are used. It would be ridiculous to remove documentation just because the IANA list is out of sync with reality. If you think IANA should be updated, then by all means, be my guest. | |||
Revision as of 03:23, 2 July 2012
Is there any reason that the entries x-dns-prefetch-control and x-ua-compatible should not be removed? They do not meet the requirements for inclusion per the spec. at this stage:
Such extensions must use a name that is identical to an HTTP header registered in the Permanent Message Header Field Registry…
Hixie: If they are implemented by software, the solution is to fix the IANA registry, not this one.
Theimp: When that's done, they can be re-added.
Hixie: That's putting theoretical purity before pragmatic documentation of interoperability.
Theimp: No, it's not. Anyone is as free to propose additions to the IANA Permanent Message Header Field Registry, as they are to edit this wiki. Document it there first, as required by the HTML spec. By all means, please document everything — but follow the standards process and begin at the beginning; not at the end.
Hixie: No. The goal is to document reality. Reality is that these fields are used. It would be ridiculous to remove documentation just because the IANA list is out of sync with reality. If you think IANA should be updated, then by all means, be my guest.