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

New metadata item with default value not written #5485

Closed
cyberduck opened this issue Nov 30, 2010 · 4 comments
Closed

New metadata item with default value not written #5485

cyberduck opened this issue Nov 30, 2010 · 4 comments
Assignees
Labels
bug fixed s3
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Nov 30, 2010

2602672 created the issue

Attempting to add new metadata filed (specifically cache-control) to files hosted on Amazon S3 does not work. The new metadata filed and value can be entered and adjusted in Cyberduck, but it does not save to the S3 server.

Editing an existing metadata field (one created from within the AWS interface) works as expected.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 30, 2010

2602672 commented

FYI - running the last nightly 3.8 (7852)

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 30, 2010

@dkocher commented

I suppose the issue that you don't make a modification to the default value. Because the value remains unchanged, it is not detected properly there was any editing even if you press Enter and the textfield looses focus.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 30, 2010

2602672 commented

Yep - you're right. If you add a new metadata field and edit an existing one at the same time the new field gets added properly.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 30, 2010

@dkocher commented

In b2dfa26.

@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
Projects
None yet
Development

No branches or pull requests

2 participants