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
When signing a request containing a "é" character for example, I end up getting a 403 Response with a SignatureDoesNotMatch error inside.
This is due to the fact that when creating the stringToSign in S3rver, the path is not URL-encoded.
It has to be URL encoded as per the AWS documentation: https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html#RESTAuthenticationExamples-8
I am making a PR to fix that.
The text was updated successfully, but these errors were encountered:
This is now fixed in v3.6.0, cheers!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
When signing a request containing a "é" character for example, I end up getting a 403 Response with a SignatureDoesNotMatch error inside.
This is due to the fact that when creating the stringToSign in S3rver, the path is not URL-encoded.
It has to be URL encoded as per the AWS documentation:
https://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html#RESTAuthenticationExamples-8
I am making a PR to fix that.
The text was updated successfully, but these errors were encountered: