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
{{ message }}
Repository navigation
feat(aws): support configurable Single/Double URI encoding in AWS SigV4 #911
Add an explicit Single/Double setting to the AWS V4 request signer.
Keep Single as the default to preserve its existing behavior for compatibility.
In Double mode, encode the original wire path once more for canonicalization, preserving structural '/' separators. Do not decode the path first.
Apply the selected encoding mode consistently to both header signing and presigning. Preserve the original request path; presigning should only append authentication fields to the query string.
For example, a wire path /a%20b/c%2Fd should produce /a%2520b/c%252Fd in Double mode. Existing escape spelling also matters: %2f becomes %252f, and %7E becomes %257E.
Tests
Cover spaces, encoded slashes, literal percent signs, non-ASCII names, lowercase escapes, and encoded unreserved characters. Check header and presigned signatures against aws-sigv4 with path normalization disabled and matching signing settings. Add regression tests for unchanged Single behavior and unchanged wire path/query bytes.
The shared helpers also serve SigV4a, so the implementation should avoid changing its existing behavior accidentally.
Activity
feat(aws): support configurable canonical URI encoding (apache#912)