Fix Content-Disposition header not working in Azure Blob storage
Prior to this commit, files downloaded in Azure Blob Storage would not have a Content-Disposition header sent, which would cause files to be saved with an unfriendly filename. https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/merge_requests/25 added support for retrieving this response header by requesting this in the Azure shared access signature (SAS) token. We now patch CarrierWave to send these custom options to the File object. We drop the dynamic parameter check in the CarrierWave patch since we have a fog-google version that supports the options. Plus, this dynamic parameter doesn't work with mocks since the mocks don't copy the exactly method signature. Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/341061 Changelog: fixed
Showing
... | @@ -129,7 +129,7 @@ gem 'fog-local', '~> 0.6' | ... | @@ -129,7 +129,7 @@ gem 'fog-local', '~> 0.6' |
gem 'fog-openstack', '~> 1.0' | gem 'fog-openstack', '~> 1.0' | ||
gem 'fog-rackspace', '~> 0.1.1' | gem 'fog-rackspace', '~> 0.1.1' | ||
gem 'fog-aliyun', '~> 0.3' | gem 'fog-aliyun', '~> 0.3' | ||
gem 'gitlab-fog-azure-rm', '~> 1.1.1', require: false | gem 'gitlab-fog-azure-rm', '~> 1.2.0', require: false | ||
# for Google storage | # for Google storage | ||
gem 'google-api-client', '~> 0.33' | gem 'google-api-client', '~> 0.33' | ||
... | ... |
Please register or sign in to comment