9017 2010-02-16 10:02:41 +0000 The origin argument should be used to determine whether Referer is to be omitted for XMLHttpRequest. I'm not a 100% sure at the moment when that would matter, but it seems safer. 2018-10-29 06:12:29 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#fetch P3 normal LC 1 contributor ian annevk christianity.webb ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32170 0 contributor 2010-02-16 10:02:41 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#fetch Comment: The origin argument should be used to determine whether Referer is to be omitted for XMLHttpRequest. I'm not a 100% sure at the moment when that would matter, but it seems safer. Posted from: 213.236.208.22 32513 1 ian 2010-02-23 01:54:23 +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: It's not safer, it's wrong. :-) The 'origin' parameter is only used for deciding if there should be an Origin header, as part of the origin privacy stuff. 32565 2 annevk 2010-02-23 11:16:54 +0000 It is also used for its value. Having said, I think this will work out fine. I cannot imagine a situation where you can get an XMLHttpRequest constructor object of which the XMLHttpRequest origin is a unique identifier but Referer would still be a useful value.