-
Notifications
You must be signed in to change notification settings - Fork 4.1k
cloud/s3: consider if we should disable signing request body #115193
Copy link
Copy link
Closed
Labels
A-disaster-recoveryC-performancePerf of queries or internals. Solution not expected to change functional behavior.Perf of queries or internals. Solution not expected to change functional behavior.O-supportWould prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docsWould prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docsP-1Issues/test failures with a fix SLA of 1 monthIssues/test failures with a fix SLA of 1 monthT-disaster-recovery
Description
Metadata
Metadata
Assignees
Labels
A-disaster-recoveryC-performancePerf of queries or internals. Solution not expected to change functional behavior.Perf of queries or internals. Solution not expected to change functional behavior.O-supportWould prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docsWould prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docsP-1Issues/test failures with a fix SLA of 1 monthIssues/test failures with a fix SLA of 1 monthT-disaster-recovery
We already send our requests over TLS, so we get little benefit from including the content body in the request signature.
For the same reasons outlined in #115189, we may benefit from skipping this and the associated
sha256.blockcalls.Jira issue: CRDB-33926