You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
… but I ran into no amount of issues, probably due to my misunderstanding of Fog. But I'm pretty sure that fog doesn't allow this query param. It would be nice to support request parameter overrides in get_object_url or even url.
The way I was trying (which failed, due to the fact that params[:query] was a string that didn't have keys — and using a hash mashed my key/value together without a = breaking the request):
The end result was that it seemed impossible to get a &response-content-disposition=attachment%3B%20filename%3Dtest.zip into the url string to be signed.
The text was updated successfully, but these errors were encountered:
That commit should fix it so that you can pass a hash as the query (with the content related stuff in there) and have it do the right thing. Will try to get a release out later this week (probably tomorrow or Thursday, but have a few more things to review/merge). Thanks!
geemus@8fb8642#L0R68 supposes that params[:query] exists, while this might not hold true. I was hacking Paperclip to expose the computed and private url of attachment and found this.
My suggested fix is to declare params[:query] ||= {} on line 66.
I was looking to create a signed url that included a
response-content-disposition
request parameter override so that I could change the filename that the browser downloaded. You can see examples of this on Amazon's documentation: http://docs.amazonwebservices.com/AmazonS3/latest/API/index.html?RESTObjectGET.html… but I ran into no amount of issues, probably due to my misunderstanding of Fog. But I'm pretty sure that fog doesn't allow this query param. It would be nice to support request parameter overrides in
get_object_url
or evenurl
.The way I was trying (which failed, due to the fact that
params[:query]
was a string that didn't have keys — and using a hash mashed my key/value together without a=
breaking the request):The end result was that it seemed impossible to get a
&response-content-disposition=attachment%3B%20filename%3Dtest.zip
into the url string to be signed.The text was updated successfully, but these errors were encountered: