From c2cb0244b6c5310d776cce0e062986c3beb0c7d0 Mon Sep 17 00:00:00 2001 From: Gregory Haynes Date: Wed, 21 Sep 2016 11:34:46 -0700 Subject: [PATCH] Remove invalid assertions for 304 resp Per the HTTP spec (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5) http 304 responses should not include entity headers. Proxies (such as apache) remove these headers (rightfully) and therefore make it impossible to test behind a proxy. Change-Id: I2e26c188e723002e8eb058cfb2d881ab858cfaa4 --- tempest/api/object_storage/test_object_services.py | 3 --- 1 file changed, 3 deletions(-) diff --git a/tempest/api/object_storage/test_object_services.py b/tempest/api/object_storage/test_object_services.py index 919f695325..8736f9a7dc 100644 --- a/tempest/api/object_storage/test_object_services.py +++ b/tempest/api/object_storage/test_object_services.py @@ -954,10 +954,7 @@ class ObjectTest(base.BaseObjectTest): # When the file is not downloaded from Swift server, response does # not contain 'X-Timestamp' header. This is the special case, therefore # the existence of response headers is checked without custom matcher. - self.assertIn('content-type', resp) - self.assertIn('x-trans-id', resp) self.assertIn('date', resp) - self.assertIn('accept-ranges', resp) # Check only the format of common headers with custom matcher self.assertThat(resp, custom_matchers.AreAllWellFormatted())