-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable cookie parsing for URLs which are IP-based, not DNS #968
Comments
I don't have opinion on this topic. One note, would it be better to allow to use different implementation and provide cookies with filtering as an extra instead of adding more parameters? |
same as @fafhrd91 |
@kxepal I don't understand you clean: are you suggest allowing ip addresses by default or forbidding? |
@asvetlov forbid as newest RFC defines and common guidelines defines. Enabling this is actually fallback to old RFCs where this is allowed, but discouraged, so I think that should be default state of things today. |
Gotcha. Will publish bug fix release soon. |
BTW what is good name for the class? |
|
@kxepal are you kidding me? |
@asvetlov Sorry, but it was too seductive to not propose (: |
Fixed by aiohttp 0.22.2 release. |
Long story short
Working on aiohttp_session I've figured out that current behavior is not convenient for development and tests writing.
Expected behaviour
Don't ignore Set-Cookie from sites with IP address in URL
It's result of #799 PR
@panda73111 could you remind why you have added the filter?
As an option we can have
StrictCookieJar
class orstrict=True
CookieJar parameter with IP filter enabled but I believe default behavior should accept cookies from IP URLs.@popravich what do you think?
The text was updated successfully, but these errors were encountered: