Actions
Bug #14005
closedRGW shouldn't send Content-Type nor Content-Length for 304 responses
% Done:
0%
Source:
other
Tags:
Backport:
hammer
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Currently if you get a 304 response (using If-None-Match in the request for instance), then you get in the response :
Content-Type: binary/octet-stream (no matter what the actual content-type of the object is)
Content-Length: 0
Those two headers shouldn't be there ... it actually breaks Safari that will refuse to play video because of this ...
Updated by Yehuda Sadeh over 8 years ago
- Assignee set to Daniel Gryniewicz
- Priority changed from Normal to High
Updated by Wido den Hollander about 8 years ago
PR to fix this: https://github.com/ceph/ceph/pull/8253
Updated by Nathan Cutler about 8 years ago
- Status changed from New to Fix Under Review
Updated by Wido den Hollander about 8 years ago
Seems like the PR was merged. Do we mark this as a fix to be ported into Jewel and backport into Hammer?
Updated by Nathan Cutler about 8 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to hammer
@Wido den Hollander: Jewel backports have not started yet. I marked the issue for hammer backport.
Updated by Nathan Cutler about 8 years ago
- Copied to Backport #15283: hammer: RGW shouldn't send Content-Type nor Content-Length for 304 responses added
Updated by Wei-Chung Cheng about 8 years ago
- Related to Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response added
Updated by Wei-Chung Cheng about 8 years ago
- Related to deleted (Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response)
Updated by Wei-Chung Cheng about 8 years ago
- Has duplicate Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response added
Updated by Nathan Cutler almost 8 years ago
- Status changed from Pending Backport to Resolved
Actions