swift/test/unit
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
..
account tests: Check proxy-logging stats on the wire 2024-06-24 11:04:44 -07:00
cli recon-cron: Tolerate missing directories 2024-03-21 14:10:14 -07:00
common Ensure correct content-type in container HEAD response 2024-11-25 10:15:04 +11:00
container reconciler: Record queue-clean-up later than old-policy-clean-up 2024-11-06 14:32:53 +00:00
obj Merge "Differentiate unlinks and outdated unlinks" 2024-11-18 01:55:28 +00:00
proxy proxy: fix is_useful_response for py2 2024-09-26 16:01:36 +01:00
test_locale py3: port the test of locale 2019-06-19 09:54:14 -07:00
__init__.py proxy: fix is_useful_response for py2 2024-09-26 16:01:36 +01:00
helpers.py Clean up watchdog threads 2024-05-02 08:30:54 -07:00