Project

General

Profile

Actions

Bug #45736

open

rgw: lack of headers in 304 response

Added by Ilsoo Byun almost 4 years ago. Updated 4 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Target version:
% Done:

0%

Source:
Community (user)
Tags:
s3 etag backport_processed
Backport:
quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
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.


Related issues 3 (2 open1 closed)

Has duplicate rgw - Fix #63507: 304 response is not RFC9110 compliantDuplicate

Actions
Copied to rgw - Backport #63960: reef: rgw: lack of headers in 304 responseIn ProgressCasey BodleyActions
Copied to rgw - Backport #63961: quincy: rgw: lack of headers in 304 responseIn ProgressCasey BodleyActions
Actions

Also available in: Atom PDF