-
-
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
Do not hang on 206 Partial Content
response with Content-Encoding: gzip
#3124
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3124 +/- ##
=======================================
Coverage 98.09% 98.09%
=======================================
Files 43 43
Lines 7833 7833
Branches 1351 1351
=======================================
Hits 7684 7684
Misses 57 57
Partials 92 92
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi.
Thanks for the contribution.
Would you add a test to make sure that the problem is fixed and will not return back by future code modifications?
Actually I was trying to reproduce it aiohttp server, but did not manage to send the required response. Luckily I found some in the wild (can be seen in #3123) Not sure how to write the test. If I understand correctly, aiohttp server does not support 206 for non-file responses. |
You can gzip the body in web handler and return a regular response with the partial body and |
OK, will try to cook something up |
Added tests. Please review again. |
thanks |
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. |
What do these changes do?
Do not raise
ContentEncodingError('deflate')
forgzip
encoding when the response is partial. This can be a valid response in case of 206 Partial Content. The bug was not reproducible with deflate or brotli encodingAre there changes in behavior for the user?
User behaviour is not affected
Related issue number
This fixes #3123
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.