wip: add skip-uri-encode param to add-aws-v4-auth-heads #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mxork
force-pushed
the
canonical-path-uri-encode
branch
from
07f05da
to
091266f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Docs say path segments need to be double url-encoded: https://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.html. S3 is exceptional, and needs to be encoded only once.
Diff as-is is a somewhat awkward attempt to drill the param through and still have S3 do the right thing.
Still needs style, testing, and coverage of
add-v4-auth-headsandaws-v4-signed-uri.Also, should probably use uri-encode/rfc-... from utils.
Also, should probably uri-encode the request uri.