[HTTPS-E Rulesets] Google Reader AU

[Matthew Fernandez]

Hi Adam/Peter,

I think I agree with Adam on this, but I'm not sure what the
alternative behaviour is. Is the alternative you're referring to
hardcoding a rule for each Google ccTLD where we see this behaviour?

With regards to this conflicting with existing rules, I have it in my
HTTPSEverywhereRules directory and haven't noticed any other Google
services falling back to HTTP. However, I realise this isn't a
comprehensive test. I looked at merging it into the existing Google
ruleset, but balked when I saw the size of it. Also, it looks like I
forgot to escape the periods in the from.

Peter, it looks as if my Google Reader account is accessible from
www.google.com.au/reader as well as www.google.com/reader so it would
not cause me problems if the .com.au HTTP redirected to the .com
HTTPS. Having said that, I have a suspicion that which domains your
Google account is accessible from may be dependent on how you signed
up, not what country you live in. Adam, maybe you can shed some light
on this.

Thanks,
Matt

On 5 May 2011 02:25, Adam Langley <agl at chromium.org> wrote:
> On Wed, May 4, 2011 at 11:31 AM, Peter Eckersley <pde at eff.org> wrote:
>> domain.  I'm sure there are others out there though...
>
> Assuming that Google HTTPS services may appear on any ccTLD is likely
> to be more future-proof than the alternative.
>
>
> Cheers
>
> AGL
>