swift/test
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
..
functional Make SLO manifest copies retain correct content-type 2016-05-23 17:25:05 +01:00
probe Merge "Import BrainSpliter directly in expirer probe" 2016-05-16 00:58:56 +00:00
unit Fix setup of manifest responses in SLO tests 2016-05-23 17:26:28 +01:00
__init__.py test/(functional/probe):Replace python print operator with print function (pep H233, py33) 2015-08-20 11:42:58 +09:00
sample.conf Merge "Add a note for functional tests with Keystone." 2016-03-18 05:08:10 +00:00