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
If you have a key with a leading slash, like /my/key.txt, then generating a presigned URL for it will produce a URL that looks like https://blah-blah.s3.amazon.com//my/key.txt?...
It's not clear to me whether the // at the start of the URL path there makes this URL technically invalid or not. However, some other libraries take the view that it is invalid. for example, the popular requests library has recently introduced behaviour that stips the double slash, and this breaks using such presigned URLs: psf/requests#6711
requests is unlikely to be the only library that has issues with such URLs.
Expected Behavior
Generate a URL that doesn't a double slash.
Current Behavior
Produces a URL where the path starts with a //
Reproduction Steps
Adapted from the reproducer in psf/requests#6711 to not be requests specific:
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Describe the bug
If you have a key with a leading slash, like
/my/key.txt
, then generating a presigned URL for it will produce a URL that looks likehttps://blah-blah.s3.amazon.com//my/key.txt?...
It's not clear to me whether the
//
at the start of the URL path there makes this URL technically invalid or not. However, some other libraries take the view that it is invalid. for example, the popularrequests
library has recently introduced behaviour that stips the double slash, and this breaks using such presigned URLs: psf/requests#6711requests
is unlikely to be the only library that has issues with such URLs.Expected Behavior
Generate a URL that doesn't a double slash.
Current Behavior
Produces a URL where the path starts with a
//
Reproduction Steps
Adapted from the reproducer in psf/requests#6711 to not be requests specific:
Possible Solution
I think the Java SDK escapes slashes in this specific case?
Additional Information/Context
No response
SDK version used
1.34.118
Environment details (OS name and version, etc.)
linux ubuntu
The text was updated successfully, but these errors were encountered: