Remove checking of Accept-Range header

Some tests fail when Accept-Range header is not present in the
response of the API. This is not necesseary as the Accept-Range
header is not mandatory according to RFC [1].

[2] https://tools.ietf.org/html/rfc7233#section-2.3

Closes-Bug: #1885723
Change-Id: I521eb4a332937328b5010df53ddab2af76090202
This commit is contained in:
Lukas Piwowarski 2020-06-30 13:16:14 +00:00 committed by Martin Kopec
parent 3800158de0
commit 4f633edd97
1 changed files with 0 additions and 2 deletions

View File

@ -76,8 +76,6 @@ class ExistsAllResponseHeaders(object):
if self.method == 'GET' or self.method == 'HEAD': if self.method == 'GET' or self.method == 'HEAD':
if 'x-timestamp' not in actual: if 'x-timestamp' not in actual:
return NonExistentHeader('x-timestamp') return NonExistentHeader('x-timestamp')
if 'accept-ranges' not in actual:
return NonExistentHeader('accept-ranges')
if self.target == 'Account': if self.target == 'Account':
if 'x-account-bytes-used' not in actual: if 'x-account-bytes-used' not in actual:
return NonExistentHeader('x-account-bytes-used') return NonExistentHeader('x-account-bytes-used')