Conflict with HTTPS Everywhere extension

[diracdeltas]

See comments to https://trac.torproject.org/projects/tor/ticket/8995.

[oldestlivingboy]

This issue is similar to #100. As in that case, I think HTTPS Everywhere's ruleset should be updated. Since www.google.com supports HTTPS now, I don't think encrypted.google.com is the canonical name for the service anymore.

[diracdeltas]

Thanks. Could you confirm that the following privacy difference between www.google.com and encrypted.google.com no longer exists?

"There is one small caveat that users should be aware of with the new encrypted-when-logged-in Google. If you click on an advertisement, and the advertiser's website is HTTP rather than HTTPS, Google will send the search terms for that specific query to the advertiser over HTTP. The encrypted.google.com domain will continue to exist and will not have that behavior: on that domain, advertisers only get to see the search that lead to a click-through if they use HTTPS." - https://www.eff.org/deeplinks/2011/10/google-encrypts-more-searches