Re:Mozilla Firefox: Rolling Out HTTPS Google search
by ComputerGuru on Wednesday May 09, 2012 @11:17PM
(#3951696)
I don't know about the spec, but in practice, you never get the referer data even when traffic flows from HTTPS to HTTPS.
[ Parent
| on HN ]
Re:Mozilla Firefox: Rolling Out HTTPS Google search
by fl3tch on Wednesday May 09, 2012 @11:23PM
(#3951713)
This is actually up to the client. In Firefox about:config, network.http.sendSecureXSiteReferrer is set to true by default, so it does send it, but you can turn it off.
Re:Mozilla Firefox: Rolling Out HTTPS Google search
by tonfa on Thursday May 10, 2012 @03:51AM
(#3952330)
Google decides what the referrer is since it redirects first to a url it controls (downgrading to http if necessary).
Re:Mozilla Firefox: Rolling Out HTTPS Google search
by thezilch on Wednesday May 09, 2012 @11:29PM
(#3951731)
In practice, this is not true. As for spec [0]:
Clients SHOULD NOT include a Referer header field in a (non-secure)
HTTP request if the referring page was transferred with a secure
protocol.
[0] http://tools.ietf.org/html/rfc2616#section-15.1.3
Re:Mozilla Firefox: Rolling Out HTTPS Google search
by cpeterso on Thursday May 10, 2012 @12:51AM
(#3951913)
Unless I'm missing something, that section only addresses HTTPS -> HTTP referrals, not HTTPS -> HTTPS.
Re:Mozilla Firefox: Rolling Out HTTPS Google search
by thezilch on Thursday May 10, 2012 @02:43AM
(#3952173)
I don't know of such a section, there is simply a section on Referer[sic] request-headers [0], at large. HTTP -> HTTP and HTTPS -> HTTPS are implied, if the only stated consideration is HTTPS -> HTTP referrals. HTTPS -> HTTPS Referer works on Google Search, which is usually of the most concern.