9603 2010-04-28 08:11:13 +0000 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. 2010-10-04 14:32:43 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#fetching-resources P3 normal LC 1 contributor ian annevk ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35273 0 contributor 2010-04-28 08:11:13 +0000 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 37759 1 ian 2010-08-24 18:49:01 +0000 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. 37760 2 ian 2010-08-24 18:49:13 +0000 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