Currently the proxy keeps iterating through
the connections in hope of finding a success even
if it already has found a tombstone (404).
This change changes the code a little bit to compare
the timestamp of a 200 and a 404, if the tombstone is
newer, then it should be returned, instead of returning
a stale 200.
Closes-Bug: #1560574
Co-Authored-By: Tim Burke <email address hidden>
Change-Id: Ia81d6832709d18fe9a01ad247d75bf765e8a89f4
Signed-off-by: Thiago da Silva <email address hidden>
Reviewed: https:/ /review. openstack. org/371150 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=8d882095375 dc53acdafafac40 aa2efc3bafbcd4
Committed: https:/
Submitter: Zuul
Branch: master
commit 8d882095375dc53 acdafafac40aa2e fc3bafbcd4
Author: Thiago da Silva <email address hidden>
Date: Thu Sep 15 16:45:06 2016 -0400
Return 404 on a GET if tombstone is newer
Currently the proxy keeps iterating through
the connections in hope of finding a success even
if it already has found a tombstone (404).
This change changes the code a little bit to compare
the timestamp of a 200 and a 404, if the tombstone is
newer, then it should be returned, instead of returning
a stale 200.
Closes-Bug: #1560574
Co-Authored-By: Tim Burke <email address hidden> fe9a01ad247d75b f765e8a89f4
Change-Id: Ia81d6832709d18
Signed-off-by: Thiago da Silva <email address hidden>