Actions
Bug #64676
openrgw: awssigv4: new trailer boundary case
Status:
Pending Backport
Priority:
High
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
sigv4 backport_processed
Backport:
quincy reef squid
Regression:
No
Severity:
2 - major
Reviewed:
Description
I observed an environment in which the maven test suite, using http, generated a trailer chunk
boundary of "0;" rather than the expected "\r\n0;"
This only arose during upload of a 0-length object.
The failing test has obviously run successfully at and since merge, this was seen only when the
current sigv4 parsing logic was taken for our downstream 7.0z1.
Updated by Matt Benjamin 2 months ago
- Status changed from In Progress to Fix Under Review
Updated by Casey Bodley 2 months ago
- Tags set to sigv4
- Backport changed from reef,quincy to quincy reef squid
Updated by J. Eric Ivancich about 2 months ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 2 months ago
- Copied to Backport #64768: squid: rgw: awssigv4: new trailer boundary case added
Updated by Backport Bot about 2 months ago
- Copied to Backport #64769: reef: rgw: awssigv4: new trailer boundary case added
Updated by Backport Bot about 2 months ago
- Copied to Backport #64770: quincy: rgw: awssigv4: new trailer boundary case added
Updated by Backport Bot about 2 months ago
- Tags changed from sigv4 to sigv4 backport_processed
Actions