Clay Gerrard fa889358ac Ensure correct content-type in container HEAD response
A failing CORS test in the gate discovered that we were responding
application/json to ?format=txt requests (which is maybe not even a
valid value for that qs param?), but only when running with
eventlet==0.38.0

This avoids the problem of backend container server HEADs no longer
having 'Content-Length: 0' by fixing the client HEAD resp headers before
we check for chunked-transfer resp.

Drive-By: refactor listing_formats to use HeaderKeyDict and always set
Content-Length explicitly

Co-Authored-By: Alistair Coles <alistairncoles@gmail.com>
Co-Authored-By: Matthew Oliver <matt@oliver.net.au>

Change-Id: If724485e1425d1481d10b9255436301e346f07e8
2024-11-25 10:15:04 +11:00
..
2024-02-07 15:48:39 -08:00
2010-07-12 17:03:45 -05:00
2024-02-07 15:48:39 -08:00
2018-03-13 12:06:07 +00:00
2022-02-10 11:17:06 -08:00
2017-11-07 15:39:25 +11:00