5 ms·
Mozilla Firefox: Rolling Out HTTPS Google search
- janesvilleseo 15y agoSo the question I have is how big of an impact is this going to have to online marketers? (Especially if Chrome/IE follow suit)
- cpeterso 15y agoThey are unhappy because websites won't see HTTP Referer headers and will have to rely on Google's webmaster services to get referral stats: https://bugzilla.mozilla.org/show_bug.cgi?id=633773#c43 https://bugzilla.mozilla.org/show_bug.cgi?id=633773#c43
- mlinksva 15y agoWill they not see the referer header if their own sites (as indexed by Google) are https? If they don't switch, puts some sort of upper bound on how much they value the referer data. (User agents aren't supposed to send referer http->https but scratch above if practice is for them not to send https->https across domains as well.)
- ComputerGuru 15y agoI don't know about the spec, but in practice, you never get the referer data even when traffic flows from HTTPS to HTTPS.
- fl3tch 15y agoThis 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.
- tonfa 15y agoGoogle decides what the referrer is since it redirects first to a url it controls (downgrading to http if necessary).
- thezilch 15y agoIn 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 http://tools.ietf.org/html/rfc2616#section-15.1.3
- cpeterso 15y agoUnless I'm missing something, that section only addresses HTTPS -> HTTP referrals, not HTTPS -> HTTPS.
- thezilch 15y agoI 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. [0] http://tools.ietf.org/html/rfc2616#section-14.36 http://tools.ietf.org/html/rfc2616#section-14.36
- yaix 15y agoRight. The article says this: "Additionally, using HTTPS helps providers like Google remove information from the referrer string."
- tonfa 15y agoYes, just checked, they strip the keywords from the referrer when using https.
- DHowett 15y agoWhy was this not done when Google started supporting https? It seems almost negligent to have not done it sooner.
- khuey 15y agoBecause you have to make sure that Google's https infrastructure can handle the load of 400 million Firefox users?
- DHowett 15y agoIt could already provably handle the load of millions of Chrome users (cf. SPDY: https). And it's not like it's totally separate from their normal http infrastructure, which could also already provably handle the load of billions of searches.
- deleted 15y ago[deleted]
- Steko 15y agoIf there's any negligence I don't see how it goes to the browser vendors and not the website.
- zobzu 15y agoMozilla has a contract with Google for this, remember? Google has to ack it for this to happen.
- cpeterso 15y agoA nice side effect of using HTTPS is that Firefox 13+ will be able to use SPDY for Google searches.
- yaix 15y agoNo REFERER header anymore, bye bye search keywords data, now only in Google Webmaster Tools... Edit -- From the article: "Additionally, using HTTPS helps providers like Google remove information from the referrer string."
- mkjones 15y agoMaybe I'm missing something, but doesn't Google redirect through an interstitial page that's always over HTTP, so you do get a referrer that says the traffic came from them?
- germane 15y agoYes, they do. But they are cutting out the keyword intentionally. There is no technical need to hide the keyword from website owners. Remarkable coincidence 1: There still is a keyword in the referrer for AdWords customers. Remarkable coincidence 2: There is a new _charged_ product called "Google Analytics Premium" that promises "more data, features and dedicated support". Shame upon him who thinks evil upon it.
- mkjones 15y agoAh, I thought they made that change for everyone a few months ago. Didn't realize it was only for https clicks.
- j_s 15y agoHmmm, I installed the Undirect Chrome extension because I got tired of the delay this causes ( https://chrome.google.com/webstore/detail/dohbiijnjeiejifbgfdhfknogknkglio https://chrome.google.com/webstore/detail/dohbiijnjeiejifbgf... ); I guess I have to choose between Google knowing which search result I clicked or the webmaster having the keyword in the referrer!
- RKearney 15y agoOr just make your site HTTPS only and the referer header is passed.
- rwar 15y agoYou can do this with chrome by adding a search engine (and making it default): https://www.google.com/search?%7Bgoogle:RLZ%7D%7Bgoogle:acceptedSuggestion%7D%7Bgoogle:originalQueryForSuggestion%7Dsourceid=chrome&ie=%7BinputEncoding%7D&q=%s&num=100 https://www.google.com/search?%7Bgoogle:RLZ%7D%7Bgoogle:acce...
- germane 15y agoThis has nothing to do with security. Removing the referrer information puts Google in the position to use (sell?) this information exclusively. While Google is collecting more and more data about users Mozilla calls it an "improvement" to keep away referrer information from website owners. This is ridiculous. So Mozilla get's its money from Google and in return they do what Google tells them.
- TomAnthony 15y agoI see your point, but Mozilla is in an impossible position. Encrypting people's search is a good idea. Mozilla should do this, and as others in this thread have pointed out, they could be chastised for not having done it. The fault is Google's who tamper with the referrer data intentionally to obscure the keyword data. They do this for the users 'privacy', but then you can still get the data if you're a paying Adwords customer. I have trouble reconciling 'privacy' and 'you can buy it'.
- driax 15y ago> I have trouble reconciling 'privacy' and 'you can buy it'. I'm not sure, but I would assume that the idea is that data from Adwords, etc. is more anonymised. You can't build a system that tracks peoples searches across visits (using cookies).
- deleted 15y ago[deleted]
- newman314 15y agoIf you want this today, you can go to http://opensearch.webos-internals.org/gtp.html http://opensearch.webos-internals.org/gtp.html using either Chrome or Firefox and make that the default search engine. As a side benefit, the config also turns SafeSearch and personalization off.
- Joe_Knapp 15y agoSmall business will suffer. Again.