- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 12 Oct 2009 06:29:14 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv32497 Modified Files: Overview.html Log Message: Allow non-IETF HTTP headers to be registered as pragmas also. (whatwg r4114) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3272 retrieving revision 1.3273 diff -u -d -r1.3272 -r1.3273 --- Overview.html 12 Oct 2009 06:08:50 -0000 1.3272 +++ Overview.html 12 Oct 2009 06:29:10 -0000 1.3273 @@ -10215,16 +10215,16 @@ any particular state in the document at a time.<h5 id="other-pragma-directives"><span class="secno">4.2.5.4 </span>Other pragma directives</h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft</i><p><dfn id="concept-http-equiv-extensions" title="concept-http-equiv-extensions">Extensions to the predefined set of pragma directives</dfn> may, under certain conditions, be registered in the <a href="http://wiki.whatwg.org/wiki/PragmaExtensions">WHATWG Wiki - PragmaExtensions page</a>. <a href="#refsWHATWGWIKI">[WHATWGWIKI]</a><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>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at + PragmaExtensions page</a>. <a href="#refsWHATWGWIKI">[WHATWGWIKI]</a><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>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>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:<dl><dt>Keyword</dt> @@ -10241,7 +10241,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"> @@ -69401,6 +69402,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,
Received on Monday, 12 October 2009 06:29:18 UTC