Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

No way to upload files with headers using Google Cloud Storage #510

Closed
the-inconvenience-store opened this issue Jun 14, 2018 · 4 comments · Fixed by #970
Closed

No way to upload files with headers using Google Cloud Storage #510

the-inconvenience-store opened this issue Jun 14, 2018 · 4 comments · Fixed by #970

Comments

@the-inconvenience-store

I'm using Google Cloud Storage and currently have to either manually or script the setting of my Content-Disposition headers. The amazon module supports this but GCS does not?
I believe it should be implemented in a similar way,

GS_HEADERS = {
    'Expires': 'Thu, 15 Apr 2010 20:00:00 GMT',
    'Cache-Control': 'max-age=86400',
    'Content-Disposition': 'attachment',
}
@sww314
Copy link
Contributor

sww314 commented Jul 24, 2018

@ReconCubed do you want something different than what was fixed in #411?
Do you want to set all headers not just Cache-control?

@the-inconvenience-store
Copy link
Author

@sww314 Yes, I'd like to be able to modify the content-disposition mainly.

@the-inconvenience-store the-inconvenience-store changed the title Not way to upload files with headers using Google Cloud Storage No way to upload files with headers using Google Cloud Storage Jul 24, 2018
@JeffreyCA
Copy link
Contributor

There's no way to set headers using Azure Storage either.

@JeffreyCA
Copy link
Contributor

JeffreyCA commented Dec 21, 2020

This is now possible on Azure as of v1.11 (see #898). Just add the following to your Django configuration:

AZURE_OBJECT_PARAMETERS = {
    'content_disposition': 'attachment'
}

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants