Cyberduck
Mountain Duck
CLI#10341 closed defect (fixed)
Copying file does not preserve metadata
| Reported by: | aspohn | Owned by: | dkocher |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.7.0 |
| Component: | s3 | Version: | 6.5.0 |
| Severity: | normal | Keywords: | |
| Cc: | Architecture: | Intel | |
| Platform: | macOS 10.13 |
Description
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
Change History (8)
comment:1 Changed 4 months ago by aspohn
- Component changed from core to s3
- Owner set to dkocher
comment:2 Changed 4 months ago by dkocher
- Summary changed from S3 Component Does Not Set Content-Type Header Appropriately to Copying file does not preserve Content-Type
comment:3 Changed 4 months ago by i1207030
comment:4 Changed 3 months ago by dkocher
- Milestone set to 7.0
- Status changed from new to assigned
comment:5 Changed 3 months ago by dkocher
- Resolution set to fixed
- Status changed from assigned to closed
In r10341.
comment:6 Changed 3 months ago by dkocher
- Summary changed from Copying file does not preserve Content-Type to Copying file does not preserve metadata
comment:7 Changed 3 months ago by dkocher
- Milestone changed from 7.0 to 6.6.3
Note: See
TracTickets for help on using
tickets.
I suggest this behavior should be preserved for files in vault (Cryptomator)