Signature does not match when S3 object has special symbols in path
nickcaballero opened this issue · comments
Calling getObject or listObjects on the S3 client with a URL that has a = in the path fails. According to diagram from AWS documentation, the URI should also be encoded, except for forward slashes.
Using folder structures like bucket/state=fl/city=orlando/data.json is fairly common.
I have a commit that seems to fix it, but it needs more testing, and we may want to rename the uriEscapePath to something else since it's a bit of a misnomer.
Sounds good, I've checked your commit, seems sound, but I'll test it more thoroughly once a PR is opened. Thanks a lot for taking the time to fix it 🙇🏻
Hey @nickcaballero, I believe this is fixed by version v0.12.3 where we explicitly addressed the URI encoding/double encoding scenarios involving spaces and special characters.
I will close this as a result, but please feel free to take it for a spin, and if you still find breaking use cases, let us know, and we'll reopen it 🙇🏻