- From: <bugzilla@jessica.w3.org>
- Date: Fri, 08 Nov 2013 10:38:10 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21264 --- Comment #4 from Hallvord R. M. Steen <hsteen@mozilla.com> --- "an issue" - let's elaborate a bit to try to figure out what the issue is, might help us resolve it.. Definition of "referrer source" (HTML5) http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html#referrer-source "A referrer source is either a Document or a URL." Algorithm for setting referer header (Fetch) http://fetch.spec.whatwg.org/#determine-referrer This algorithm doesn't cover anything XHR-specific (which is fine if the XHR spec sets "referrer source" explicitly). Does it? Yes: open() step 2.4 says "Set referrer source to document." But then there's send() step 10 which says request should be initialized with (among other things) referrer referrer source and this is marked as an open issue. So it seems either we have to 1) be able to pass a referrer source with the request and have Fetch do the right thing, or 2) reference the determine-referrer algorithm at this point and say something like referrer the result of calling the [determine referrer algorithm] for the given referrer source with the stuff in brackets appropriately linked. I'd suggest doing #1 - change http://fetch.spec.whatwg.org/#concept-request to say the request has an associated referrer or referrer source. It seems less work overall if we don't have to reference the determine-referrer algorithm from lots of other specs all over the place. Then we just drop the "pending issue" from the XHR spec and resolve this bug. How does it sound? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 8 November 2013 10:38:12 UTC