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

Not implemented fully metadata support on S3 #274

Open
thekandor opened this issue Mar 28, 2014 · 3 comments
Open

Not implemented fully metadata support on S3 #274

thekandor opened this issue Mar 28, 2014 · 3 comments
Assignees

Comments

@thekandor
Copy link

When we create object on S3 as one of option we can add only few headers which will be added as a metadata without conversion with 'x-amz-meta-' etc. Current version support only Content-Type, Content-Length. Method update_object from SDK isn't also used. But there are situations when that behaviour is needed, like setting object metadata which force Content-Disposition:attachment. Currently this is impossible. And both, old and new, versions of SDK allow for that in some cases. This may be even solved by adding those cases like Content-Type were solved. This bug is especially painfull, because IE in some cases (docx and this family) have problem with proper MimeType recognize (treat them as zip files).

@christheyounger
Copy link

Any update on this? It's a real pain.

@barat
Copy link

barat commented Sep 2, 2015

I think that only way is to fork it and add own method to set Content-Type header :(

@gggeek
Copy link

gggeek commented Oct 15, 2015

A sub-issue of #108 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants