openstack/swift
Code Issues Proposed changes
2078f6328e
swift/test/unit/proxy/controllers
History
Alistair Coles 12dd408823 Put correct Etag and Accept-Ranges in EC 304 and 416 responses 
When using an EC policy, 304 responses to conditional GETs
are missing the Accept-Ranges header and have the wrong ETag
value. 412 responses also have the wrong etag.

416 responses to ranged GETs also have the wrong ETag.

This patch ensures behaviour with EC policy is consistent
with replication policy:

  - 304 and 416 responses have correct etag and Accept-Ranges
  - 412 responses have correct Etag but no Accept-Ranges

Co-Authored-By: Mahati Chamarthy <mahati.chamarthy@gmail.com>
Co-Authored-By: Thiago da Silva <thiago@redhat.com>

Closes-Bug: #1496234
Closes-Bug: #1558197
Closes-Bug: #1558193
Change-Id: Ic21317b9e4f632f0751133a3383eb5487379e11f
2016-03-17 11:47:33 +00:00
..
__init__.py re-use headers_to_container_info on container GET 2012-11-01 18:46:47 -07:00
test_account.py Use 201 insted of 200 in PUT test case 2016-02-22 16:10:09 +09:00
test_base.py Move HeaderKeyDict to avoid an inline import 2016-03-07 12:26:48 -08:00
test_container.py dry out container unittests 2016-02-23 09:17:56 +00:00
test_info.py Remove simplejson from tests 2015-05-28 16:05:57 -07:00
test_obj.py Put correct Etag and Accept-Ranges in EC 304 and 416 responses 2016-03-17 11:47:33 +00:00