Project

General

Profile

Actions
Copy link

Bug #14005

closed

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

Added by Sylvain Munaut over 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Daniel Gryniewicz
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 2 (0 open — 2 closed)

Has duplicate rgw - Bug #15119: Civetweb responds with Content-Type with a 304 Not Modified responseDuplicate03/14/2016

Actions
Copied to rgw - Backport #15283: hammer: RGW shouldn't send Content-Type nor Content-Length for 304 responsesResolvedWei-Chung ChengActions
Actions
Copy link
 #1

Updated by Yehuda Sadeh over 8 years ago

  • Assignee set to Daniel Gryniewicz
  • Priority changed from Normal to High
Actions
Copy link
 #3

Updated by Nathan Cutler about 8 years ago

  • Status changed from New to Fix Under Review
Actions
Copy link
 #4

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?

Actions
Copy link
 #5

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.

Actions
Copy link
 #6

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
Actions
Copy link
 #7

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
Actions
Copy link
 #8

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)
Actions
Copy link
 #9

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
Actions
Copy link
 #10

Updated by Nathan Cutler over 7 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF