-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
aiohttp barfs on dropbox download with "Invalid character in chunk size" #10322
Comments
Is there a redirect involved? Might be due to recoding... The traceback shows the server responding with HTTP 400. |
yes redirects in play
|
Try passing You may also disable the redirects and walk them manually, verifying that the |
@jonathon-love also note that curl goes for HTTP/2 which aiohttp won't upgrade. That's another difference. |
thanks for your help. adding
and the addition of
one thing worth noting is that this is a
if i change this to a with thanks |
Is the issue present with I'll try and reproduce in a couple of days. |
it works when |
I wonder if there's something we're missing, to tell the C parser that it is a HEAD response. I suspect it's trying to parse a full response.. |
Describe the bug
aiohttp barfs on a dropbox download, that other software (i.e. curl) doesn't seem to have difficulty with.
To Reproduce
Expected behavior
200 OK
Logs/tracebacks
aiohttp Version
multidict Version
propcache Version
yarl Version
OS
linux, macOS
Related component
Client
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: