K2V: double urlencoding #574
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#574
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-k2v-urlencoding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a proposal fix for #573. Since rusoto_signature double-urlencodes paths for all APIs except S3, then we will do the same when verifying signatures client-side. This page suggest that path segments must indeed be url-encoded twice (once by http, once by the signature calculation algorithm): https://docs.aws.amazon.com/rolesanywhere/latest/userguide/authentication-sign-process.html
EDIT: wrote an extensive comment in the source code with more explanation, go read that.
Fix #573
de39da1103
to92fdeb1c56
92fdeb1c56
to4420db7310