-
Notifications
You must be signed in to change notification settings - Fork 26
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
Copy from Cache To Store Strips Content Type #36
Comments
Thanks for this report. I am not sure why setting those additional attributes removes the content type, I will try to troubleshoot this. |
This is a bug in the |
This is a workaround due to googleapis/google-cloud-ruby#4254 It should not have any visible impact as it does not create any additional request. Also added a test for uploading from an existing GCS file, ensuring this is correctly fixed. Fixes #36
I just released 2.0.1 with a workaround for this issue, until this is fixed upstream. |
I have opened PR googleapis/google-cloud-ruby#4275 to fix this issue in general in |
Fix released in google-cloud-storage v1.24.0. |
The original image is successfully being stored in the 'cache' storage, and subsequently when it comes time to upload, it makes it successfully to the
copy
methodHowever, the original file that gets copied over to the main 'store' storage will lose it's Content Type.
I tested using the copy functionality directly using the google-cloud-storage gem. The content type remains.
I have been unable to track down the issue.
Update 1
I was able to narrow it down by deleting this do loop - It appears those options are overwriting the content type.
Update 2
Setting any custom headers as described on the readme will cause the content-type to be emptied
The text was updated successfully, but these errors were encountered: