Project

General

Profile

Bug #14005

RGW shouldn't send Content-Type nor Content-Length for 304 responses

Added by Sylvain Munaut about 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
High
Target version:
-
% 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 ...


Related issues

Duplicated by rgw - Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response Duplicate 03/14/2016
Copied to rgw - Backport #15283: hammer: RGW shouldn't send Content-Type nor Content-Length for 304 responses Resolved

History

#1 Updated by Yehuda Sadeh almost 7 years ago

  • Assignee set to Daniel Gryniewicz
  • Priority changed from Normal to High

#3 Updated by Nathan Cutler over 6 years ago

  • Status changed from New to Fix Under Review

#4 Updated by Wido den Hollander over 6 years ago

Seems like the PR was merged. Do we mark this as a fix to be ported into Jewel and backport into Hammer?

#5 Updated by Nathan Cutler over 6 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to hammer

@Wido: Jewel backports have not started yet. I marked the issue for hammer backport.

#6 Updated by Nathan Cutler over 6 years ago

  • Copied to Backport #15283: hammer: RGW shouldn't send Content-Type nor Content-Length for 304 responses added

#7 Updated by Wei-Chung Cheng over 6 years ago

  • Related to Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response added

#8 Updated by Wei-Chung Cheng over 6 years ago

  • Related to deleted (Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response)

#9 Updated by Wei-Chung Cheng over 6 years ago

  • Duplicated by Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified response added

#10 Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF