Actions
Bug #38055
closedrgw: GET/HEAD and PUT operations on buckets w/lifecycle expiration configured do not return x-amz-expiration header
% Done:
0%
Source:
Tags:
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
The required behavior is documented here:
https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectHEAD.html
https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html
Updated by Matt Benjamin about 5 years ago
- Status changed from In Progress to Fix Under Review
Updated by Casey Bodley about 5 years ago
- Status changed from Fix Under Review to 17
Updated by Casey Bodley almost 5 years ago
- Status changed from 17 to In Progress
Updated by Casey Bodley over 4 years ago
- Status changed from 7 to Pending Backport
- Backport set to luminous mimic nautilus
@Matt Li, do all 3 backports sound appropriate to you?
Updated by Patrick Donnelly over 4 years ago
- Copied to Backport #41122: nautilus: rgw: GET/HEAD and PUT operations on buckets w/lifecycle expiration configured do not return x-amz-expiration header added
Updated by Patrick Donnelly over 4 years ago
- Copied to Backport #41123: luminous: rgw: GET/HEAD and PUT operations on buckets w/lifecycle expiration configured do not return x-amz-expiration header added
Updated by Patrick Donnelly over 4 years ago
- Copied to Backport #41124: mimic: rgw: GET/HEAD and PUT operations on buckets w/lifecycle expiration configured do not return x-amz-expiration header added
Updated by Nathan Cutler about 4 years ago
@Casey The backports do not seem appropriate, because @Matt Li 's fix uses the "fmt" submodule, which was added post-nautilus. Can you confirm or deny that theory?
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions