Actions
Bug #45736
openrgw: lack of headers in 304 response
% Done:
0%
Source:
Community (user)
Tags:
s3 etag backport_processed
Backport:
quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When returning 304(not modified) in response to a conditonal GET request, s3 returns response with headers like cache-control, etag, etc(https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorS3Origin.html#RequestS3ConditionalGETs).
HTTP RFC(https://tools.ietf.org/html/rfc7232#section-4.1) also explains that 304 responses have to contain headers guiding cache update.
But rgw does not return these headers.
Updated by Casey Bodley 5 months ago
- Status changed from New to Fix Under Review
- Tags set to s3 etag
- Backport set to quincy reef
- Pull request ID changed from 35284 to 54587
Updated by Casey Bodley 5 months ago
- Has duplicate Fix #63507: 304 response is not RFC9110 compliant added
Updated by Konstantin Shalygin 5 months ago
- Tracker changed from Fix to Bug
- Target version set to v19.0.0
- Source set to Community (user)
- Backport changed from quincy reef to pacific quincy reef
- Regression set to No
- Severity set to 3 - minor
- Affected Versions v16.2.14, v17.2.7, v18.2.1 added
Updated by Casey Bodley 4 months ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from pacific quincy reef to quincy reef
Updated by Backport Bot 4 months ago
- Copied to Backport #63960: reef: rgw: lack of headers in 304 response added
Updated by Backport Bot 4 months ago
- Copied to Backport #63961: quincy: rgw: lack of headers in 304 response added
Updated by Backport Bot 4 months ago
- Tags changed from s3 etag to s3 etag backport_processed
Actions