From c1bf3f399948dd503598428306a5838190d03241 Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Tue, 27 Oct 2020 17:35:12 +0000 Subject: [PATCH] s3: remove Dot from encoding #4704 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Before this change the s3 backend used Dot in its encoding. This meant it was impossible to read and write a file called "." as we were translating it to its unicode equivalent. This means that the integration tests weren't testing the ability to save and load files called "." and ".." at all. This change removes the encoding which means that files called "." (which need to be named with the unicode equivalent "．" on the command line) can be used. --- backend/s3/s3.go | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/backend/s3/s3.go b/backend/s3/s3.go index 6981e7824..ce1d6e8e5 100644 --- a/backend/s3/s3.go +++ b/backend/s3/s3.go @@ -1190,8 +1190,7 @@ rclone does if you know the bucket exists already. // - trailing / encoding // so that AWS keys are always valid file names Default: encoder.EncodeInvalidUtf8 | - encoder.EncodeSlash | - encoder.EncodeDot, + encoder.EncodeSlash, }, { Name: "memory_pool_flush_time", Default: memoryPoolFlushTime,