You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note here how the SignatureProvided is: qZ0ARjdg1ISat42nhi2Xns+PP2g=
which doesn't match qZ0ARjdg1ISat42nhi2Xns%2BPP2g%3D
from the original request. It looks like it is encoding the %, which is breaking it.
If I take that exact same original url and load it with a browser, or Postman, or python requests, it works fine. So there is something that aiohttp is doing differently.
Expected behavior
I expect the image to load the same way it does in other libraries/browsers.
@bdraco I tired and it doesn't help because there is no redirect happening. Also, looks like the setting is deprecated. It might be related to #9567 as that might be query string related.
Describe the bug
I am trying to load a captcha image, and it is failing.
To Reproduce
Go to this page:
https://www.amazon.com/ap/cvf/request?arb=b3b3093e-694e-4eca-b0f2-935471c78975
If will load an amazon captcha. Inspect the url of the image. It will look something like:
https://opfcaptcha-prod.s3.amazonaws.com/506ebe7024fd4a8e85878e40a3f3cfeb.jpg?AWSAccessKeyId=AKIA5WBBRBBB27TDSHCK&Expires=1731123498&Signature=qZ0ARjdg1ISat42nhi2Xns%2BPP2g%3D
Note how
Signature
isqZ0ARjdg1ISat42nhi2Xns%2BPP2g%3D
Now try to load the url with aiohttp. You will get a 403 response with something like:
Note here how the
SignatureProvided
is:qZ0ARjdg1ISat42nhi2Xns+PP2g=
which doesn't match
qZ0ARjdg1ISat42nhi2Xns%2BPP2g%3D
from the original request. It looks like it is encoding the
%
, which is breaking it.If I take that exact same original url and load it with a browser, or Postman, or python requests, it works fine. So there is something that aiohttp is doing differently.
Expected behavior
I expect the image to load the same way it does in other libraries/browsers.
Logs/tracebacks
Python Version
aiohttp Version
multidict Version
propcache Version
yarl Version
OS
macOS 14.7
Related component
Client
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: