Alistair Coles 0007353a39 s3api: do not set x-timestamp header ...

There's no need for the s3api controllers to set the x-timestamp
header in requests. Furthermore, it may be inappropriate for the s3api
middleware to set the x-timestamp header if in doing so it overwrites
a value set by a previous middleware.

In the case of an object copy, the last-modified time required for the
response body can be obtained from the swift copy (PUT) request
response.  The proxy server app copies the PUT request.timestamp to
the PUT response.last_modified.

Related-Change: Iab68f4b596dfa7f23bc587fbde859d854faff87f
Related-Change: I4dacc11ec086fdd2e9bb3f68295f2ebaea68bede
Change-Id: I4f46ae51579aafb9f511ddec8f2bce5fd5498ba5
Signed-off-by: Alistair Coles <alistairncoles@gmail.com>

2026-01-27 11:57:47 +00:00

2.0 KiB

Raw Permalink Blame History

View Raw