We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm trying to do a HEAD request to a service that returns a 303 redirect. aiohttp then does a full GET on the new location.
aiohttp should instead do a HEAD on the new URL.
aiohttp does a GET on the new URL
The code responsible is here: https://github.com/KeepSafe/aiohttp/blob/master/aiohttp/client.py#L228 This references this PR from the requests library: https://github.com/kennethreitz/requests/pull/269/files. However, the requests library is preserving the HEAD method for subsequent requests.
The text was updated successfully, but these errors were encountered:
Makes sense. Would you provide a fix?
Sorry, something went wrong.
Fix redirects for HEAD requests.
baaf9d3
Fixes: aio-libs#1146
Fix redirects for HEAD requests. (#1147)
118826c
Fixes: #1146
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.
Successfully merging a pull request may close this issue.
Long story short
I'm trying to do a HEAD request to a service that returns a 303 redirect. aiohttp then does a full GET on the new location.
Expected behaviour
aiohttp should instead do a HEAD on the new URL.
Actual behaviour
aiohttp does a GET on the new URL
The code responsible is here: https://github.com/KeepSafe/aiohttp/blob/master/aiohttp/client.py#L228
This references this PR from the requests library: https://github.com/kennethreitz/requests/pull/269/files. However, the requests library is preserving the HEAD method for subsequent requests.
The text was updated successfully, but these errors were encountered: