fix: exclude content-length and content-type from GetObjectRange signed headers - #459
Open
dardourimohamed wants to merge 1 commit into
Open
fix: exclude content-length and content-type from GetObjectRange signed headers#459dardourimohamed wants to merge 1 commit into
dardourimohamed wants to merge 1 commit into
Brownian Motion v0 / Brownian Motion
succeeded
May 6, 2026 in 0s
PR effectively addresses header signing issue for GetObjectRange requests.
Risk: Medium · Confidence: 80%
Details
Brownian Motion (Brass)
Recommendation: Proceed
Summary: PR effectively addresses header signing issue for GetObjectRange requests.
Risk: Medium · Confidence: 80%
Highlights
- Good test coverage
- Clear commit history
Next actions
- Keep: the change to exclude content-length and content-type headers for GetObjectRange.
- Drop: any additional complexity not directly related to this fix.
- Add: documentation on the implications of header changes for different backends.
Reflection questions
- What core assumption underpins this PR's approach?
- How does this change align with the project's longer-term goals?
- Could there be a simpler way to achieve the primary objective here?
Loading