Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto Gzip Decompress on Google Cloud #9400

Closed
cyberduck opened this issue Apr 3, 2016 · 1 comment
Closed

Auto Gzip Decompress on Google Cloud #9400

cyberduck opened this issue Apr 3, 2016 · 1 comment
Assignees
Labels
enhancement googlestorage Google Cloud Storage Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

ef73de4 created the issue

When downloading gzip compressed files via cybderduck, they don't get automatically uncompressed.
It would be supercool if they did.

When storing files in Google Cloud, you can optionally store them compressed as gzip.
This can be done using gsutil with the -z or -Z flags.
There's no modification to the filename to signify this change...no ".gz" suffix.
Viewing the metadata of a file via Cyberduck I can see a few headers that could be used to identify and uncompress relevant files.
They have headers such as:
stored-content-encoding: gzip
Content-encoding: gzip

So if cyberduck sees these headers, it could potentially do an automatic decompression.

Potentially this could be expanded further to support compression on upload as well.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

When a response is compressed (advertised with Content-Encoding header) we decompress the entity received. It could be that the resource is double compressed (regardless of the transfer encoding) which we do not handle.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement googlestorage Google Cloud Storage Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants