docs: clarify cookie domain normalization #17590
Merged
Conversation
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
vhashimotoo
approved these changes
Apr 2, 2019
MarshallOfSound
approved these changes
Apr 2, 2019
|
Release Notes Persisted
|
|
I have automatically backported this PR to "4-1-x", please check out #17662 |
|
I have automatically backported this PR to "5-0-x", please check out #17663 |
kiku-jw
pushed a commit
to kiku-jw/electron
that referenced
this pull request
May 16, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Resolves #17564.
Clarifies that Chrome normalizes cookie domains to make them valid for subdomains, so
hostOnlywill only be true for cookies which are not specified with a domain.cc @deepak1556
Checklist
npm testpassesRelease Notes
Notes: Clarified cookie domain normalization behavior by Chromium in cookie documentation.