Fix #12939
closed
Content-Type header should have correct initial capitals
Added by Robin Johnson over 8 years ago.
Updated over 8 years ago.
Affected Versions:
Ceph - v0.51,
v0.52a,
v0.53a,
v0.53b,
v0.54a,
v0.54b,
v0.55a,
v0.56,
v0.57a,
v0.57b,
v0.58,
v0.59,
v0.60,
v0.61 - Cuttlefish,
v0.62a,
v0.62b,
v0.63,
v0.64,
v0.65,
v0.66,
v0.67 - Dumpling,
v0.67rc,
v0.67rc-continued,
v0.68,
v0.68 - continued,
v0.69,
v0.70,
v0.71-rc1,
v0.72 Emperor,
v0.73,
v0.74,
v0.75,
v0.76,
v0.77,
v0.78,
sprint,
sprint2,
sprint3,
v0.80rc,
sprint4,
v0.81,
v0.82,
v0.83,
v0.84,
v0.85,
v0.86,
v0.87,
v0.88,
v0.89,
v0.90,
v0.91,
v0.92,
v0.93 - Last Hammer Sprint,
v9.0.2,
v9.0.3,
v9.0.4,
v9.1.0,
10.0.1,
0.95,
Ceph - v0.80.10,
Ceph - v0.80.11,
Ceph - v0.94.2,
Ceph - v0.94.3,
Ceph - v0.94.4
Description
Some S3/HTTP clients do not correctly implement that header field names are supposed to be case insensitive. Fix "Content-type" to "Content-Type".
CyberDuck/JetS3 was one such client, which is now also fixed https://trac.cyberduck.io/ticket/8999upstream.
This is a very long-standing subtle bug, having first being entered in the very first version of RGW.
Tracing commits with it, newest to oldest
5cc92bb2 2015-04-09 src/rgw/rgw_rest.cc
fe6cd9bc 2013-10-22 src/rgw/rgw_rest.cc
a9c9f96b 2012-09-19 src/rgw/rgw_rest.cc
9b7f223a 2011-04-15 src/rgw/rgw_rest.cc
c9135519 2011-03-08 src/s3/s3rest.cc
536a8b64 2009-07-17 src/s3/s3gw.cc
b5dcdd86 2009-06-24 src/s3/s3gw.cc
9b4e957b 2009-06-19 src/s3/s3gw.cc
4faa62da 2009-06-18 src/s3/s3gw.cc
d30cb706 2009-06-16 src/s3/s3gw.cc
2f2cb893 2009-06-12 src/s3/s3gw.cc
e5e12647 2009-06-12 src/s3/s3gw.cc FIRST VERSION!
Originally reported to Dreamhost per DHO-1137.
- Status changed from New to In Progress
- Status changed from In Progress to Pending Backport
- Backport changed from hammer, firefly, infernalis to hammer, firefly
removing infernalis from the Backport field: before infernalis is released, scheduling something to be in infernalis is done by issuing a pull request against the infernalis branch or the master branch and setting the "infernalis" milestone of the pull request. There is no cherry-picking involved at any stage.
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF