Skip to content
Permalink
Browse files

[] (0) Allow non-IETF HTTP headers to be registered as pragmas also.

git-svn-id: http://svn.whatwg.org/webapps@4114 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 12, 2009
1 parent 53b9b69 commit db548c54f9830ff7d5bafed247749e6c5ee0082d
Showing with 56 additions and 33 deletions.
  1. +18 −11 complete.html
  2. +18 −11 index
  3. +20 −11 source
@@ -11649,16 +11649,18 @@ <h5 id=other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma dir
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
@@ -11679,7 +11681,8 @@ <h5 id=other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma dir

<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 @@ <h2 class=no-num id=references>References</h2><!--REFS-->
<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,
29 index
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

<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>

<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,
31 source
@@ -12126,16 +12126,19 @@ people expect to have work and what is necessary.
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
@@ -12158,7 +12161,8 @@ people expect to have work and what is necessary.

<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>

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

0 comments on commit db548c5

Please sign in to comment.
You can’t perform that action at this time.