[HTTPS-Everywhere] Google Searches

[Nick Cross]

Hi,

Thanks for the reply.

The halfway point seems like a reasonable solution. The additional 
functionality on country specific sites seems to be the issue and I 
guess until Google provides encrypted.google.[co.uk] then using 
https://www.google.co.uk may be the only option

Currently I have aded my own rule and disable the built in google search 
rule - this seems to work fine.

Thanks

Nick


On 25/02/12 00:06, Peter Eckersley wrote:
> I'm wavering on the encrypted.google.com / www.google.com issue.
>
> Another thing that is pushing me is this:
>
> https://trac.torproject.org/projects/tor/ticket/5152
>
> One halfway point might be to use the native non-US cctld sites when the user
> types them or is redirected there, but stick with encrypted.google.com for US
> users.
>
> On Tue, Feb 21, 2012 at 10:16:37PM +0000, Nick Cross wrote:
>>
>> Hi,
>>
>> I know the search uses encrypted.google.com which according to the
>> FAQ supplies slightly better security.
>>
>> However, if I use http://www.google.com or https://www.google.com it
>> reroutes me to the country specific site of http://www.google.co.uk
>> or https://www.google.co.uk and most importantly I get the option to
>> "show pages from the uk" which I find invaluable when searching.
>>
>> I understand you will not change httpseverywhere to use
>> https://www.google.[co.uk|com] instead of encrypted.google.com but
>> could you perhaps consider making it configurable?
>>
>> Currently my wife just turns off httpseverywhere just to get
>> searches working correctly!
>>
>> Do custom rules overrule the built in rules?
>>
>> Thanks!
>> _______________________________________________
>> HTTPS-everywhere mailing list
>> HTTPS-everywhere at mail1.eff.org
>> https://mail1.eff.org/mailman/listinfo/https-everywhere
>