Rescue when there's no extension in the remotable (#6358)
* Rescue when there's no extension in the remotable Sometimes the remotable is pointing to a directory with no file extension. Maybe it should not be expecting to identify based on extensions to begin with, but since it's the case, it should be ready for it. * Fix codeclimate issue * Check if filename is nil instead of rescueing exception Suggestion made in the PR * Avoid concatenation issue if filename is nil If filename is nil, extname was undefined * Invert condition Address PR comments
This commit is contained in:
parent
6dcf96271e
commit
9aba44ea79
|
@ -28,7 +28,11 @@ module Remotable
|
||||||
matches = response.headers['content-disposition']&.match(/filename="([^"]*)"/)
|
matches = response.headers['content-disposition']&.match(/filename="([^"]*)"/)
|
||||||
filename = matches.nil? ? parsed_url.path.split('/').last : matches[1]
|
filename = matches.nil? ? parsed_url.path.split('/').last : matches[1]
|
||||||
basename = SecureRandom.hex(8)
|
basename = SecureRandom.hex(8)
|
||||||
extname = File.extname(filename)
|
extname = if filename.nil?
|
||||||
|
''
|
||||||
|
else
|
||||||
|
File.extname(filename)
|
||||||
|
end
|
||||||
|
|
||||||
send("#{attachment_name}=", StringIO.new(response.to_s))
|
send("#{attachment_name}=", StringIO.new(response.to_s))
|
||||||
send("#{attachment_name}_file_name=", basename + extname)
|
send("#{attachment_name}_file_name=", basename + extname)
|
||||||
|
|
Loading…
Reference in New Issue