Project

General

Profile

Bug #4124

Using "response-content-type" arguments causes duplicated Content-Type in response

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

Status:
Resolved
Priority:
High
Assignee:
Target version:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
bobtail
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

Title says it all ... If I do a GET and use the"response-content-type" to ensure the 'Content-Type' header in the response, then I'll get two 'Content-Type' headers back. One with the value that ceph has internally and one with what I asked.

0001-radosgw-Fix-duplicate-Content-Type-when-using-respon.patch View - Proposed patch (1.13 KB) Sylvain Munaut, 02/14/2013 05:59 AM

History

#1 Updated by Sylvain Munaut over 7 years ago

Here's a fix that worked for me.

#2 Updated by Yehuda Sadeh over 7 years ago

  • Status changed from New to 12
  • Assignee set to Yehuda Sadeh
  • Backport set to bobtail

#3 Updated by Ian Colle over 7 years ago

  • Status changed from 12 to Fix Under Review
  • Priority changed from Normal to High

#4 Updated by Ian Colle over 7 years ago

  • Status changed from Fix Under Review to New
  • Assignee changed from Yehuda Sadeh to caleb miles

Not seen on Apache.

#5 Updated by Sylvain Munaut over 7 years ago

Apache might be filtering the duplicate header I guess. I use lighttpd as a fastcgi front end.

#6 Updated by Ian Colle over 7 years ago

  • Assignee changed from caleb miles to Yehuda Sadeh

#7 Updated by Ian Colle over 7 years ago

  • Target version set to v0.61 - Cuttlefish

#8 Updated by Yehuda Sadeh over 7 years ago

  • Status changed from New to Resolved

Merged in, commit:9b953aa4100eca5de2319b3c17c54bc2f6b03064

Also available in: Atom PDF