You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
Added option --server-gzip as workaround for this.
It's look like different providers/servers implement different GZIP logic.
AWS S3 send compressed only files uploaded with Content-Encoding: gzip.
But probably your servers sends all files compressed with gzip. Probably it's not a S3 server configuration, but your reverse proxy configuration, between client and server.
What s3 server (provider) are you using?
If it's self hosted do you have reverse proxies (like nginx)? If yes, can you please show proxy gzip configuration?
i think the offending commit is this 8e3a72e
it looks like it download content as gzip but leaving it as is.
we rollback to previous version and it works.
the data in my case is .html file, raw text. it's getting downloaded as gzip content which can't be display with nginx.
my expectation: s3sync should keep the file as is.
To do this, maybe we can do additional head request to check the content type and see if decompression is required?
The text was updated successfully, but these errors were encountered: