diff options
| author | mkwst <mkwst@chromium.org> | 2016-03-15 03:07:52 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-03-15 10:09:31 +0000 |
| commit | e1a295845cbc338a564dc04e6e3e69b29ba7862f (patch) | |
| tree | 00535f752a8faa939a4d646ca0215423e93e8ee6 /chrome/browser/search_engines/ui_thread_search_terms_data.cc | |
| parent | 752434c777d2e7b445e37629bf89ecc7c38c7c5c (diff) | |
| download | chromium_src-e1a295845cbc338a564dc04e6e3e69b29ba7862f.zip chromium_src-e1a295845cbc338a564dc04e6e3e69b29ba7862f.tar.gz chromium_src-e1a295845cbc338a564dc04e6e3e69b29ba7862f.tar.bz2 | |
SameSite: Implement 'Strict'/'Lax' attribute parsing.
https://tools.ietf.org/html/draft-west-first-party-cookies-06 introduced
the notion of "Strict" or "Lax" enforcement of the "SameSite" attribute.
This patch implements the infrastructure changes necessary to support
that distinction, but does not yet implement the behavioral change
(that is, after this patch, `SameSite` will be rejected, while
`SameSite=Strict` and `SameSite=Lax` will have the same behavior that
`SameSite` alone has today).
Most of this patch is occupied with the fairly mechanical process of
swapping out a new 'CookieSameSite' enum for the existing boolean in
various constructors and setters. The most interesting piece is the
change to the storage backend, which now stores 0, 1, or 2 in the
database to represent the possible values, rather than 0 or 1 to
represent the boolean.
BUG=459154
Review URL: https://codereview.chromium.org/1773133002
Cr-Commit-Position: refs/heads/master@{#381201}
Diffstat (limited to 'chrome/browser/search_engines/ui_thread_search_terms_data.cc')
0 files changed, 0 insertions, 0 deletions