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

Jump to bottom

Invalid metadata sent when overwriting file #8674

Closed
cyberduck opened this issue Mar 17, 2015 · 12 comments
Closed

Invalid metadata sent when overwriting file #8674

cyberduck opened this issue Mar 17, 2015 · 12 comments
Assignees
@dkocher
Labels
azure Azure Protocol Implementation bug worksforme
Milestone
4.7.3

Comments

@cyberduck
Copy link
Collaborator

29c5808 created the issue

I upload a file to azure. Some days later, I make a change locally, and upload the file via cyberduck. It pops up saying "already exists, overwrite?" and I say yes. All completes and looks like all ok, but the file contents are not actually updated. Happy to provide extra details, screenshots, log files. Please let me know how I can help to resolve this.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows.

@cyberduck
Copy link
Collaborator Author

29c5808 commented

I understand that the log window does not work for azure blob storage transfers. The log drawer is therefore blank. Is there another way to obtain logs?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed missing error reporting for failure closing output stream and thus committing blob in e956087.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The actual error is

The metadata specified is invalid. It has characters that are not permitted.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Regression from 1c4db05.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fix and test in e87c33a.

@cyberduck
Copy link
Collaborator Author

b742f49 commented

I have used the hidden setting in Terminal.app:

defaults write ch.sudo.cyberduck azure.metadata.default "Cache-Control=public,max-age=1"

to set custom Cache-Control to "1" on our Azure server.
When I upload a file, everything is good and the Cache-Control metadata is set correctly.
But when i try and overwrite the file, the Cache-Control metadata gets changed to the same metadata value that is in the Content-Type field.

I have made quick YouTube video to demonstrate this: https://youtu.be/Id3ttnRVIQA

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you reproduce this issue with the latest snapshot build available?

@cyberduck
Copy link
Collaborator Author

b742f49 commented

Yes, unfortunately :/

https://youtu.be/Zsa6kPchS7M

Replying to [comment:8 dkocher]:

Can you reproduce this issue with the latest snapshot build available?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See also #8679.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Updated upstream dependency in 18366.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available.

@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.
Assignees

@dkocher dkocher

Labels
azure Azure Protocol Implementation bug worksforme
Projects
None yet
Milestone
4.7.3
Development

No branches or pull requests
2 participants
@dkocher @cyberduck