Actions
Bug #4124
closedUsing "response-content-type" arguments causes duplicated Content-Type in response
% Done:
0%
Source:
Community (user)
Tags:
Backport:
bobtail
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
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.
Files
Updated by Sylvain Munaut about 11 years ago
- File 0001-radosgw-Fix-duplicate-Content-Type-when-using-respon.patch 0001-radosgw-Fix-duplicate-Content-Type-when-using-respon.patch added
Here's a fix that worked for me.
Updated by Yehuda Sadeh about 11 years ago
- Status changed from New to 12
- Assignee set to Yehuda Sadeh
- Backport set to bobtail
Updated by Ian Colle about 11 years ago
- Status changed from 12 to Fix Under Review
- Priority changed from Normal to High
Updated by Ian Colle about 11 years ago
- Status changed from Fix Under Review to New
- Assignee changed from Yehuda Sadeh to caleb miles
Not seen on Apache.
Updated by Sylvain Munaut about 11 years ago
Apache might be filtering the duplicate header I guess. I use lighttpd as a fastcgi front end.
Updated by Ian Colle about 11 years ago
- Assignee changed from caleb miles to Yehuda Sadeh
Updated by Ian Colle about 11 years ago
- Target version set to v0.61 - Cuttlefish
Updated by Yehuda Sadeh about 11 years ago
- Status changed from New to Resolved
Merged in, commit:9b953aa4100eca5de2319b3c17c54bc2f6b03064
Actions