Re:Search leakage is not FUD. Google et al., please fix it.
by othermaciej on Monday January 24, 2011 @01:51PM
(#2136198)
Not sending the Referer header at all can break some sites, probably more than is acceptable to do by default. But stripping the query part of the Referer header might be reasonable. Probably the main side effect of that would be to make Google mad. (P.S. the header is called "Referer", not "HTTP_REFERER").
Re:Search leakage is not FUD. Google et al., please fix it.
by nkurz on Monday January 24, 2011 @03:33PM
(#2136637)
Which sites would break, and why? (genuine question, not contrariness) I've always assumed that cross-site Referer is sufficiently brittle that one cannot depend on it, since it's isn't there if one enters a URL by hand or arrives via a redirect. And while I like it for use within a site, it seems that Cookies have taken over for most uses.
Sorry about the sloppiness with HTTP_REFERER vs Referer. You are correct --- I tend to think of it from the CGI point of view rather than browser. Browser sends Referer as an HTTP header, which web servers commonly set in the environment as HTTP_REFERER. Thus the question should be "Why not have browsers default to not sending the HTTP Referer header?"
It also seems worth noting that if for some reason you wish to continue using Google instead of DDG, and if you are concerned about the potential privacy issues, you can already change your browser not to send the referer header:
http://kb.mozillazine.org/Network.http.sendRefererHeader
https://chrome.google.com/extensions/detail/dkpkjedlegmelkog...