ISSUE-33: [withdrawn] spec requires non-compliant Referer header
ping-referer
[withdrawn] spec requires non-compliant Referer header
- State:
- CLOSED
- Product:
- HTML 5 spec
- Raised by:
- Julian Reschke
- Opened on:
- 2008-02-12
- Description:
- The specification currently requires use of an HTTP Referer header value ("#PING") which is not allowed as per RFC2616, Section 14.36:
"The URI MUST NOT include a fragment." -- <http://tools.ietf.org/html/rfc2616#section-14.36>
Related mailing list thread: <http://lists.w3.org/Archives/Public/public-html/2008Feb/0144.html>
- Related Actions Items:
- No related actions
- Related emails:
- Minutes HTML WG 11 February 2010 (from rubys@intertwingly.net on 2010-02-11)
- {minutes} HTML WG issue-tracking telcon 2008-06-19 (from mike@w3.org on 2008-06-25)
- {minutes} HTML WG issue-tracking telcon 2008-06-05 (from mike@w3.org on 2008-06-06)
- ISSUE-33 (ping-referer): spec requires non-compliant Referer header [HTML 5 spec] (from sysbot+tracker@w3.org on 2008-02-12)
Related notes:
Apparently this has been removed from the spec: <http://html5.org/tools/web-apps-tracker?from=1234&to=1235>
Julian Reschke, 5 Jun 2008, 17:35:56overtaken by changes in the spec; the offending text is no longer there
Dan Connolly, 19 Jun 2008, 16:23:43Display change log