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

Copying file does not preserve metadata #10341

Closed
cyberduck opened this issue May 30, 2018 · 3 comments
Closed

Copying file does not preserve metadata #10341

cyberduck opened this issue May 30, 2018 · 3 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

eee4cdc created the issue

Setup:

Create an index.html file and upload from the local file system. content-type is set to text/html as expected

Steps to reproduce:

From the Cyberduck browser open up a second S3 bucket and drag/copy the recently uploaded file with text/html content-type to another mapped S3 bucket and although the file is successfully copied the content type will be set to binary/octet-stream instead of the expected text/html

@cyberduck
Copy link
Collaborator Author

b1df552 commented

I suggest this behavior should be preserved for files in vault (Cryptomator)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 1624262.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@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
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants