Ceph » rgw

awsv4 streaming signatures use a variation of rfc 2616 chunked encoding, which includes provisoins for multiple keyword/value pairs. Only one is presently defined for awsv4, "chunk-signature". The current code in rgw to decode this header just assumes there is one keyword/value pair and does very limited checking even on that. To be more "future-proof", this code ought to have more robust parsing logic, and ought to be able to tolerate the addition of other unspecified fields without breaking.

As a minor technical note: note that this is not the same as transfer-encoding: chunked. It is possible to employ both transfer-encoding: chunked and awsv4 streaming signatures ("double chunking"). When this combination is fed through haproxy, the chunked transfer encoding is redone, but the unencoded data stream including awsv4 streaming signatures chunks must remain intact.