This repository has been archived by the owner on Apr 3, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 211
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix CHECK failure that equivalent cookies are not found
If strict secure cookies is enabled, if a cookie is set that matches an already existing secure cookie, it will mark the insertion as having found an equivalent cookie. Unfortunately, this is not entirely accurate, as an "equivalent cookie" more strictly means the domain and path attributes match as well. Thus, this inadvertently can cause a failure of a CHECK that verifies that there are not equivalent cookies in the store. The fix for this is to just change the strict secure portion of the matching to only set the insertion as having found equivalent cookies if it passes an additional IsEquivalent() check. BUG=569943 Review URL: https://codereview.chromium.org/1525073003 Cr-Commit-Position: refs/heads/master@{#365557}
- Loading branch information
1 parent
9302c23
commit a9a0d48
Showing
3 changed files
with
28 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters