Treat exact domain match cookies on public suffixes as host cookies.

Treat exact domain match cookies on public suffixes as host cookies.

Historically, we've rejected any cookie with a `domain` attribute for
hosts that we treat as public suffixes. This patch loosens that stance
by treating cookies whose domain attribute exactly matches the host as
host cookies.

This matches the language in step 5 of section 5.3 of RFC 6265
(https://tools.ietf.org/html/rfc6265#section-5.3), and
matches both Firefox and IE's behavior.

BUG=56211, 551906
R=jochen@chromium.org,mmenke@chromium.org

Committed: https://crrev.com/e99453bd606cfba6902d82d1e363826d21b0c6a8
Cr-Commit-Position: refs/heads/master@{#358523}

[Mike West, 2015-11-06 13:39:13]

Jochen, Matt, would you mind taking a look at this small change to our cookie
behavior?

[Mike West, 2015-11-06 13:39:20]

Description was changed from

==========
Treat exact domain match cookies on public suffixes as host cookies.

Historically, we've rejected any cookie with a `domain` attribute for
hosts that we treat as public suffixes. This patch loosens that stance
by treating cookies whose domain attribute exactly matches the host as
host cookies.

This matches the language in step 5 of section 8.3 of RFC 6252, and
matches both Firefox and IE's behavior.

BUG=551906
R=jochen@chromium.org,mmenke@chromium.org
==========

to

==========
Treat exact domain match cookies on public suffixes as host cookies.

Historically, we've rejected any cookie with a `domain` attribute for
hosts that we treat as public suffixes. This patch loosens that stance
by treating cookies whose domain attribute exactly matches the host as
host cookies.

This matches the language in step 5 of section 8.3 of RFC 6252, and
matches both Firefox and IE's behavior.

BUG=56211,551906
R=jochen@chromium.org,mmenke@chromium.org
==========

[mmenke, 2015-11-06 17:44:48]

On 2015/11/06 13:39:13, Mike West wrote:
> Jochen, Matt, would you mind taking a look at this small change to our cookie
> behavior?

RFC 6252 doesn't have a section 8.3. 
https://tools.ietf.org/html/rfc6252#section-8

[Mike West, 2015-11-06 17:54:44]

Description was changed from

==========
Treat exact domain match cookies on public suffixes as host cookies.

Historically, we've rejected any cookie with a `domain` attribute for
hosts that we treat as public suffixes. This patch loosens that stance
by treating cookies whose domain attribute exactly matches the host as
host cookies.

This matches the language in step 5 of section 8.3 of RFC 6252, and
matches both Firefox and IE's behavior.

BUG=56211,551906
R=jochen@chromium.org,mmenke@chromium.org
==========

to

==========
Treat exact domain match cookies on public suffixes as host cookies.

Historically, we've rejected any cookie with a `domain` attribute for
hosts that we treat as public suffixes. This patch loosens that stance
by treating cookies whose domain attribute exactly matches the host as
host cookies.

This matches the language in step 5 of section 5.3 of RFC 6265 
(https://tools.ietf.org/html/rfc6265#section-5.3), and
matches both Firefox and IE's behavior.

BUG=56211,551906
R=jochen@chromium.org,mmenke@chromium.org
==========

[Mike West, 2015-11-06 17:55:26]

On 2015/11/06 at 17:44:48, mmenke wrote:
> On 2015/11/06 13:39:13, Mike West wrote:
> > Jochen, Matt, would you mind taking a look at this small change to our
cookie
> > behavior?
> 
> RFC 6252 doesn't have a section 8.3. 
https://tools.ietf.org/html/rfc6252#section-8

*ahem* The ".3" was correct. The rest was nuts. :) 
https://tools.ietf.org/html/rfc6265#section-5.3 is what I meant. I've updated
the CL description and added that link.

[Mike West, 2015-11-06 20:06:33]

The CQ bit was checked by mkwst@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-11-06 20:22:11]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1414603010/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1414603010/20001

[commit-bot: I haz the power, 2015-11-06 20:49:44]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-06 20:49:48]

Dry run: This issue passed the CQ dry run.

[jochen (gone - plz use gerrit), 2015-11-07 06:09:26]

lgtm

[Mike West, 2015-11-07 10:27:05]

The CQ bit was checked by mkwst@chromium.org

[commit-bot: I haz the power, 2015-11-07 10:27:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1414603010/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1414603010/20001

[commit-bot: I haz the power, 2015-11-07 10:33:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-11-07 10:34:31]

Patchset 2 (id:??) landed as
https://crrev.com/e99453bd606cfba6902d82d1e363826d21b0c6a8
Cr-Commit-Position: refs/heads/master@{#358523}