swift/test/unit
Alistair Coles 7b706926a8 Fix setup of manifest responses in SLO tests
The swift_bytes param is removed from the content-type
in the proxy object controller, so the SLO unit tests should
not be registering GET responses with FakeSwift that have
swift_bytes appended to the content-type.

Nor should submanifest segment dicts have swift_bytes appended to
their content-type values.

Also adds a test for the object controller and container server
handling of SLO swift_bytes.

Change-Id: Icf9bd87eee25002c8d9728b16e60c8347060f320
2016-05-23 17:26:28 +01:00
..
account change default ports for servers 2016-04-29 14:47:38 -04:00
cli change default ports for servers 2016-04-29 14:47:38 -04:00
common Fix setup of manifest responses in SLO tests 2016-05-23 17:26:28 +01:00
container Fix setup of manifest responses in SLO tests 2016-05-23 17:26:28 +01:00
obj Merge "Fix bug expirer unexpectedly deletes object created after x-delete-at" 2016-05-13 02:39:57 +00:00
proxy Fix setup of manifest responses in SLO tests 2016-05-23 17:26:28 +01:00
test_locale monkeypatch thread for keystoneclient 2015-11-03 16:36:19 +01:00
__init__.py change default ports for servers 2016-04-29 14:47:38 -04:00