Skip to content
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

Properly parse Accept-Encoding #1322

Closed
asvetlov opened this issue Oct 19, 2016 · 2 comments
Closed

Properly parse Accept-Encoding #1322

asvetlov opened this issue Oct 19, 2016 · 2 comments
Labels

Comments

@asvetlov
Copy link
Member

Right now aiohttp checks Accept-Encoding header by in check (substring finding).

Proper implementation should respect weights (q=0.5 etc.).

The same strategy should be used for parsing other Accept- headers.

@asvetlov
Copy link
Member Author

Don't want to do it right now -- parsing is not very useful since I've decided to not support automatic global compression

@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant