Do not filter cookies if unsafe flag provided#1005
Merged
asvetlov merged 2 commits intoaio-libs:masterfrom Jul 26, 2016
Merged
Conversation
Member
|
Shame on me, I've missed the second IP address check. |
Member
|
Will be fixed in aiohttp 0.22.3 |
asvetlov
pushed a commit
that referenced
this pull request
Jul 26, 2016
* Add test for unsafe cookies jar * Remove code duplication and make base class for testing CookieJar
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What do these changes do?
For the testing purposes or when user is aware about what he is doing it's handy to be able provide unsafe cookie jar (so cookies will be preserved even for domain specified as IP address, e.g. 127.0.0.1)
Are there changes in behavior for the user?
Now cookies right in place
Checklist