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 9603 - If the origin parameter does not match the Document origin the Referer header should also be excluded. Alternatively a way to omit the Referer header would be good for CORS.
Summary: If the origin parameter does not match the Document origin the Referer header...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-28 08:11 UTC by contributor
Modified: 2010-10-04 14:32 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-04-28 08:11:13 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#fetching-resources

Comment:
If the origin parameter does not match the Document origin the Referer header
should also be excluded. Alternatively a way to omit the Referer header would
be good for CORS.

Posted from: 58.1.224.28 by annevk@opera.com
Comment 1 Ian 'Hixie' Hickson 2010-08-24 18:49:01 UTC 
To omit the Referer header, you just have to say that the Referer header isn't sent. (See for instance the "noreferrer" link type, which does this.) There's not much more I can do in HTML5, since HTTP doesn't provide suitable hooks here.
Comment 2 Ian 'Hixie' Hickson 2010-08-24 18:49:13 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: see comment 1