This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7861 - requirements for meta/http-equiv extensions
Summary: requirements for meta/http-equiv extensions
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-09 18:23 UTC by Julian Reschke
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:

Attachments

Description Julian Reschke 2009-10-09 18:23:59 UTC 
"4.2.5.4 Other pragma directives

Extensions to the predefined set of pragma directives may, under certain conditions, be registered in the WHATWG Wiki PragmaExtensions page. [WHATWGWIKI]

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

This goes further than the IETF requirements defined in RFC 3864. 

Recommendation: just state that the header needs to be registered with IANA; 
*potentially* requiring a registration in the permanent registry.
Comment 1 Ian 'Hixie' Hickson 2009-10-20 21:55:45 UTC 
I updated this a while back.