commit 12dd408823df158359e99fb01716f2059140c5c9
Author: Alistair Coles <email address hidden>
Date: Wed Mar 16 17:41:30 2016 +0000
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
Reviewed: https:/ /review. openstack. org/293633 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=12dd408823d f158359e99fb017 16f2059140c5c9
Committed: https:/
Submitter: Jenkins
Branch: master
commit 12dd408823df158 359e99fb01716f2 059140c5c9
Author: Alistair Coles <email address hidden>
Date: Wed Mar 16 17:41:30 2016 +0000
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 <email address hidden>
Co-Authored-By: Thiago da Silva <email address hidden>
Closes-Bug: #1496234 f0751133a3383eb 5487379e11f
Closes-Bug: #1558197
Closes-Bug: #1558193
Change-Id: Ic21317b9e4f632