- From: Takeshi Yoshino <notifications@github.com>
- Date: Wed, 15 Nov 2017 03:51:13 +0000 (UTC)
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 15 November 2017 03:51:45 UTC
IIRC, up to now, we haven't received any request from developers to send a referrer. At least, WebKit (and therefore Blink) has implemented it from scratch than reusing the existing HTTP stack and didn't add anything more than what's specified in RFC 6455. Later, we added Cache-Control, etc. in response to some analysis, interop bug, user requests, but referrer wasn't. As WebSockets are specified to always send the origin, it's ok to send a referrer including only the origin (though it's not useful as there's also the Origin header), but sending a full referrer would be a new addition to the web platform which developers may not expect. So, my gut feeling is that we shouldn't make any change without users' voice but make the spec aligned with the browsers' current behavior. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/630#issuecomment-344478048
Received on Wednesday, 15 November 2017 03:51:45 UTC