Fix https://m.gmail.com/ and https://m.googlemail.com/, which don't return a

Fix https://m.gmail.com/ and https://m.googlemail.com/, which don't return a
matching CN even with SNI.

BUG=80642
TEST=TransportSecurityStateTest.Preloaded
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=83199

[Chris Evans, 2011-04-27 04:15:55]

(Whoever sees it first)
Annoying. I'll file a server-side bug but for now it needs to be fixed.

[agl, 2011-04-27 13:58:35]

LGTM

[Chris Evans, 2011-04-27 19:58:44]

On 2011/04/27 13:58:35, agl wrote:
> LGTM

https://www.gmail.com/ and https://www.googlemail.com/ DO work with SNI (with
the CN www.gmail.com and www.googlemail.com respectively, instead of any kind of
wildcard) so I'll include them and land.

[agl, 2011-04-27 20:06:12]

On Wed, Apr 27, 2011 at 3:58 PM,  <cevans@chromium.org> wrote:
> https://www.gmail.com/ and https://www.googlemail.com/ DO work with SNI
> (with
> the CN www.gmail.com and www.googlemail.com respectively, instead of any
> kind of
> wildcard) so I'll include them and land.

If you haven't bugged secops about this although, let me know.


Cheers

AGL

[agl, 2011-04-27 20:09:11]

On Wed, Apr 27, 2011 at 4:06 PM, Adam Langley <agl@chromium.org> wrote:
> If you haven't bugged secops about this although, let me know.

s/although/already/



AGL

[Chris Evans, 2011-04-27 20:09:37]

On 2011/04/27 20:06:12, agl wrote:
> On Wed, Apr 27, 2011 at 3:58 PM,  <mailto:cevans@chromium.org> wrote:
> > https://www.gmail.com/ and https://www.googlemail.com/ DO work with SNI
> > (with
> > the CN http://www.gmail.com and http://www.googlemail.com respectively,
instead of any
> > kind of
> > wildcard) so I'll include them and land.
> 
> If you haven't bugged secops about this although, let me know.

I haven't yet. Did you want to?

I was hoping that www.gmail.com might return a *.gmail.com CN and have made this
change GFE-mapping-only. But... seems not.


Cheers
Chris

> 
> 
> Cheers
> 
> AGL