Bug #14005
closed
RGW shouldn't send Content-Type nor Content-Length for 304 responses
Added by Sylvain Munaut over 8 years ago.
Updated almost 8 years ago.
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 ...
- Assignee set to Daniel Gryniewicz
- Priority changed from Normal to High
- Status changed from New to Fix Under Review
Seems like the PR was merged. Do we mark this as a fix to be ported into Jewel and backport into Hammer?
- 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.
- Copied to Backport #15283: hammer: RGW shouldn't send Content-Type nor Content-Length for 304 responses added
- Related to Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response added
- Related to deleted (Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response)
- Has duplicate Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response added
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF