[html5] r4114 - [] (0) Allow non-IETF HTTP headers to be registered as pragmas also.
whatwg at whatwg.org
whatwg at whatwg.org
Sun Oct 11 23:40:08 PDT 2009
Author: ianh
Date: 2009-10-11 23:40:06 -0700 (Sun, 11 Oct 2009)
New Revision: 4114
Modified:
complete.html
index
source
Log:
[] (0) Allow non-IETF HTTP headers to be registered as pragmas also.
Modified: complete.html
===================================================================
--- complete.html 2009-10-12 06:19:46 UTC (rev 4113)
+++ complete.html 2009-10-12 06:40:06 UTC (rev 4114)
@@ -11649,17 +11649,19 @@
conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
- <p>Such extensions must use a name that is identical to a
- previously-registered HTTP header defined in an RFC, and must have
- behavior identical to that described for the HTTP header. Pragma
- directives corresponding to headers describing metadata, or not
- requiring specific user agent processing, must not be registered;
- instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata
- names</a>. Pragma directions corresponding to headers that affect
- the HTTP processing model (e.g. caching) must not be registered, as
- they would result in HTTP-level behavior being different for user
- agents that implement HTML than for user agents that do not.</p>
+ <p>Such extensions must use a name that is identical to a HTTP
+ header registered in the Permanent Message Header Field Registry,
+ and must have behavior identical to that described for the HTTP
+ header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
+ <p>Pragma directives corresponding to headers describing metadata,
+ or not requiring specific user agent processing, must not be
+ registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma
+ directions corresponding to headers that affect the HTTP processing
+ model (e.g. caching) must not be registered, as they would result in
+ HTTP-level behavior being different for user agents that implement
+ HTML than for user agents that do not.</p>
+
<p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
any time to add a pragma directive satisfying these conditions. Such
registrations must specify the following information:</p>
@@ -11679,7 +11681,8 @@
<dt>Specification</dt>
- <dd>A link to an IETF RFC defining the corresponding HTTP header.</dd>
+ <dd>A link to the specification defining the corresponding HTTP
+ header.</dd>
</dl><div class=impl>
@@ -84973,6 +84976,10 @@
<dd><cite><a href=http://www.iana.org/assignments/character-sets>Character
Sets</a></cite>. IANA, May 2007.</dd>
+ <dt id=refsIANAPERMHEADERS>[IANAPERMHEADERS]</dt>
+ <dd><cite><a href=http://www.iana.org/assignments/message-headers/perm-headers.html>Permanent
+ Message Header Field Names</a></cite>. IANA, October 2009.</dd>
+
<dt id=refsIEEE754>[IEEE754]</dt>
<dd><cite><a href="http://ieeexplore.ieee.org/servlet/opac?punumber=4610933">IEEE
Standard for Floating-Point Arithmetic (IEEE 754)</a></cite>. IEEE,
Modified: index
===================================================================
--- index 2009-10-12 06:19:46 UTC (rev 4113)
+++ index 2009-10-12 06:40:06 UTC (rev 4114)
@@ -11485,17 +11485,19 @@
conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
- <p>Such extensions must use a name that is identical to a
- previously-registered HTTP header defined in an RFC, and must have
- behavior identical to that described for the HTTP header. Pragma
- directives corresponding to headers describing metadata, or not
- requiring specific user agent processing, must not be registered;
- instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata
- names</a>. Pragma directions corresponding to headers that affect
- the HTTP processing model (e.g. caching) must not be registered, as
- they would result in HTTP-level behavior being different for user
- agents that implement HTML than for user agents that do not.</p>
+ <p>Such extensions must use a name that is identical to a HTTP
+ header registered in the Permanent Message Header Field Registry,
+ and must have behavior identical to that described for the HTTP
+ header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
+ <p>Pragma directives corresponding to headers describing metadata,
+ or not requiring specific user agent processing, must not be
+ registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma
+ directions corresponding to headers that affect the HTTP processing
+ model (e.g. caching) must not be registered, as they would result in
+ HTTP-level behavior being different for user agents that implement
+ HTML than for user agents that do not.</p>
+
<p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
any time to add a pragma directive satisfying these conditions. Such
registrations must specify the following information:</p>
@@ -11515,7 +11517,8 @@
<dt>Specification</dt>
- <dd>A link to an IETF RFC defining the corresponding HTTP header.</dd>
+ <dd>A link to the specification defining the corresponding HTTP
+ header.</dd>
</dl><div class=impl>
@@ -76007,6 +76010,10 @@
<dd><cite><a href=http://www.iana.org/assignments/character-sets>Character
Sets</a></cite>. IANA, May 2007.</dd>
+ <dt id=refsIANAPERMHEADERS>[IANAPERMHEADERS]</dt>
+ <dd><cite><a href=http://www.iana.org/assignments/message-headers/perm-headers.html>Permanent
+ Message Header Field Names</a></cite>. IANA, October 2009.</dd>
+
<dt id=refsIEEE754>[IEEE754]</dt>
<dd><cite><a href="http://ieeexplore.ieee.org/servlet/opac?punumber=4610933">IEEE
Standard for Floating-Point Arithmetic (IEEE 754)</a></cite>. IEEE,
Modified: source
===================================================================
--- source 2009-10-12 06:19:46 UTC (rev 4113)
+++ source 2009-10-12 06:40:06 UTC (rev 4114)
@@ -12126,17 +12126,20 @@
PragmaExtensions page</a>. <a
href="#refsWHATWGWIKI">[WHATWGWIKI]</a></p>
- <p>Such extensions must use a name that is identical to a
- previously-registered HTTP header defined in an RFC, and must have
- behavior identical to that described for the HTTP header. Pragma
- directives corresponding to headers describing metadata, or not
- requiring specific user agent processing, must not be registered;
- instead, use <span title="concept-meta-extensions">metadata
- names</span>. Pragma directions corresponding to headers that affect
- the HTTP processing model (e.g. caching) must not be registered, as
- they would result in HTTP-level behavior being different for user
- agents that implement HTML than for user agents that do not.</p>
+ <p>Such extensions must use a name that is identical to a HTTP
+ header registered in the Permanent Message Header Field Registry,
+ and must have behavior identical to that described for the HTTP
+ header. <a href="#refsIANAPERMHEADERS">[IANAPERMHEADERS]</a></p>
+ <p>Pragma directives corresponding to headers describing metadata,
+ or not requiring specific user agent processing, must not be
+ registered; instead, use <span
+ title="concept-meta-extensions">metadata names</span>. Pragma
+ directions corresponding to headers that affect the HTTP processing
+ model (e.g. caching) must not be registered, as they would result in
+ HTTP-level behavior being different for user agents that implement
+ HTML than for user agents that do not.</p>
+
<p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
any time to add a pragma directive satisfying these conditions. Such
registrations must specify the following information:</p>
@@ -12158,7 +12161,8 @@
<dt>Specification</dt>
- <dd>A link to an IETF RFC defining the corresponding HTTP header.</dd>
+ <dd>A link to the specification defining the corresponding HTTP
+ header.</dd>
</dl>
@@ -93706,6 +93710,11 @@
href="http://www.iana.org/assignments/character-sets">Character
Sets</a></cite>. IANA, May 2007.</dd>
+ <dt id="refsIANAPERMHEADERS">[IANAPERMHEADERS]</dt>
+ <dd><cite><a
+ href="http://www.iana.org/assignments/message-headers/perm-headers.html">Permanent
+ Message Header Field Names</a></cite>. IANA, October 2009.</dd>
+
<dt id="refsIEEE754">[IEEE754]</dt>
<dd><cite><a
href="http://ieeexplore.ieee.org/servlet/opac?punumber=4610933">IEEE
More information about the Commit-Watchers
mailing list