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
requests 2.32.0 introduced a change #6644 that strips double /.
This has introduced an issue where generated presigned urls for s3 keys that start with a / can no longer be used. requests now strips that second / meaning that the key is modified and the signature does not match resulting in 403 errors. We can adjust to remove the leading / in our keys but this may be affecting other users or use cases
Expected Result
To be able to use presigned_urls for s3 keys with leading "/"
Actual Result
URL that was passed was modified resulting in a 403 error response from aws
requests 2.32.0 introduced a change #6644 that strips double /.
This has introduced an issue where generated presigned urls for s3 keys that start with a / can no longer be used. requests now strips that second / meaning that the key is modified and the signature does not match resulting in 403 errors. We can adjust to remove the leading / in our keys but this may be affecting other users or use cases
Expected Result
To be able to use presigned_urls for s3 keys with leading "/"
Actual Result
URL that was passed was modified resulting in a 403 error response from aws
Reproduction Steps
System Information
The text was updated successfully, but these errors were encountered: