2f607cd319
s3api bucket listing elements currently have LastModified values with millisecond precision. This is inconsistent with the value of the Last-Modified header returned with an object GET or HEAD response which has second precision. This patch reduces the precision to seconds in bucket listings and upload part listings. This is also consistent with observation of an aws listing response. The last modified values in the swift native listing *up* to the nearest second to be consistent with the seconds-precision Last-Modified time header that is returned with an object GET or HEAD. However, we continue to include millisecond digits set to 0 in the last-modified string, e.g.: '2014-06-10T22:47:32.000Z'. Also, fix the last modified time returned in an object copy response to be consistent with the last modified time of the object that was created. Previously it was rounded down, but it should be rounded up. Change-Id: I8c98791a920eeedfc79e8a9d83e5032c07ae86d3 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| s3_test_client.py | ||
| test_acl.py | ||
| test_bucket.py | ||
| test_multi_delete.py | ||
| test_multi_upload.py | ||
| test_object.py | ||
| test_presigned.py | ||
| test_service.py | ||
| test_versioning.py | ||
| utils.py | ||