Nick Craig-Wood f7e3115955 s3: fix Wasabi HEAD requests returning stale data by using only 1 transport ... In this commit fc5b14b620 s3: Added `--s3-disable-http2` to disable http/2 We created our own transport so we could disable http/2. However the added function is called twice meaning that we create two HTTP transports. This didn't happen with the original code because the default transport is cached by fshttp. Rclone normally does a PUT followed by a HEAD request to check an upload has been successful. With the two transports, the PUT and the HEAD were being done on different HTTP transports. This means that it wasn't re-using the same HTTP connection, so the HEAD request showed the previous object value. This caused rclone to declare the upload was corrupted, delete the object and try again. This patch makes sure we only create one transport and use it for both PUT and HEAD requests which fixes the problem with Wasabi. See: https://forum.rclone.org/t/each-time-rclone-is-run-1-3-fails-2-3-succeeds/22545		2021-03-05 15:34:56 +00: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: fix Wasabi HEAD requests returning stale data by using only 1 transport	2021-03-05 15:34:56 +00:00
v2sign.go	s3: fix copy multipart with v2 auth failing with 'SignatureDoesNotMatch'	2021-01-27 14:43:02 +00:00