http-equiv

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Sat, 20 Dec 2008 11:08:21 +0100
• To: "public-html@w3.org" <public-html@w3.org>
• Message-ID: <494CC415.6010903@gmx.de>

Hi,

feedback on "Define how to register new http-equiv values. (credit: ma) 
(whatwg r2548)":

<http://www.whatwg.org/specs/web-apps/current-work/#other-pragma-directives>:

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

HTTP headers do not need to be defined in RFCs, there's a registry for 
it. See <http://tools.ietf.org/html/rfc4229>, 
<http://www.iana.org/assignments/message-headers/prov-headers.html>, and 
<http://www.iana.org/assignments/message-headers/perm-headers.html>.

BR, Julian

Received on Saturday, 20 December 2008 10:09:05 UTC