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

Defaults for metadata #5364

Open
cyberduck opened this issue Oct 21, 2010 · 9 comments
Open

Defaults for metadata #5364

cyberduck opened this issue Oct 21, 2010 · 9 comments
Assignees
Labels
enhancement low priority s3 AWS S3 Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

ba57b2b created the issue

Summary

Amazon S3 files can have associated metadata (basically, HTTP headers).

Cyberduck lets you view and edit this metadata, which works fine.

However, I would like to have certain metadata applied to every S3 upload, without having to go in and change it after the fact. I expect this is a common requirement for CloudFront users, as the Cache-Control header is very important.

To support this, Cyberduck would need to support setting defaults for S3 uploads. For example, in the Edit > Preferences > S3 dialog, you could add controls for setting default headers. For comparison, see Transmit (on OS X) or CloudBerry Explorer for Amazon S3 (on Windows). Both of these allow the user to set default headers for S3 uploads.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Note that you can select multiple files at once to change the metadata at once for all.

@cyberduck
Copy link
Collaborator Author

ba57b2b commented

I did see that. One of my use cases is for graphic designers to be able to upload product images to Amazon S3. I don’t want to rely on them setting the metadata.

Even if you know how to set the metadata, it is a nice convenience. I would compare it to the defaults for Preferences > Transfers > Permissions. Even though permissions can be set manually later, it’s convenient to have them set by default.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Currently only possible using a hidden configuration option as of f438f5c. Multiple headers must be separated using a whitespace delimiter. Key and value of a header are seperated with =. For example if you want to add a HTTP header for Cache-Control and one named Creator you would set

defaults write ch.sudo.cyberduck s3.metadata.default "Cache-Control=public,max-age=86400 Creator=Cyberduck"

Must think about a user interface for this.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Should add table to edit default metadata in S3 tab of preferences. Note that as of 870639c you can recursively apply metadata to objects in a bucket or folder.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We should also provide an option for default metadata for Cloud Files and Azure.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:6 dkocher]:

We should also provide an option for default metadata for Cloud Files and Azure.

In c98ce48.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Documentation for S3, Cloud Files and Azure.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone 4.2 deleted

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#8624 closed as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement low priority s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants