Nick Craig-Wood cf0bf159ab s3: try to keep the maximum precision in ModTime with --user-server-modtime ... Before this change if --user-server-modtime was in use the ModTime could change for an object as we receive it accurate to the nearest ms in listings, but only accurate to the nearest second in HEAD and GET requests. Normally AWS returns the milliseconds as .000 in listings, but if versions are in use it may not. Storj S3 also seems to return milliseconds. This patch tries to keep the maximum precision in the last modified time, so it doesn't update a last modified time with a truncated version if the times were the same to the nearest second. See: https://forum.rclone.org/t/cache-fingerprint-miss-behavior-leading-to-false-positive-stalen-cache/33404/		2022-10-12 09:18:10 +01:00
..
gen_setfrom.go	s3: refactor to use generated code instead of reflection to copy structs	2022-08-05 16:45:23 +01:00
s3_internal_test.go	all: fix spelling across the project	2022-08-30 11:16:26 +02:00
s3_test.go	s3: fix SetModTime on GLACIER/ARCHIVE objects and implement set/get tier	2019-09-14 09:18:55 +01:00
s3.go	s3: try to keep the maximum precision in ModTime with --user-server-modtime	2022-10-12 09:18:10 +01:00
setfrom.go	s3: refactor to use generated code instead of reflection to copy structs	2022-08-05 16:45:23 +01:00
v2sign.go	s3: fix copy multipart with v2 auth failing with 'SignatureDoesNotMatch'	2021-01-27 14:43:02 +00:00