-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
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
The path encoding fails on : #14
Comments
@orasimus this is actually how the Amazon services work – you can check it yourself if you like. |
@orasimus – only S3 will decode the querystring before escaping it again – all the other services do not try to decode entities. And because the character |
@orasimus You can read more info on it all here: aws/aws-sdk-js#853 (comment) |
@orasimus If you don't wish to have this behaviour because you're testing or using it in your own service, you can use |
Thanks for the comment. I tried looking at the code yesterday, but I guess it was too early in the morning as I missed that. :) |
Hi! Thanks for the commits regarding the path escaping.
The signing still fails if the path contains a
:
. It gets transformed into%3A
earlier and then on line 219:path.push(encodeRfc3986(querystring.escape(piece)))
querystring.escape turns it into
%253A
.So signing calls to e.g. http://domain.com/product/foo:123 fails.
The text was updated successfully, but these errors were encountered: