search

fluent-ffmpeg / node-fluent-ffmpeg

A fluent API to FFMPEG (http://www.ffmpeg.org)
MIT License
7.85k stars 874 forks source link

S3 bucket signed url is not working #843

Open ahmed-sharief5 opened 6 years ago

ahmed-sharief5 commented 6 years ago

I am using s3 bucket signed url in place of the input path. Its showing 'ffmpeg exited with code 1 no such file or directory'

ocramot commented 5 years ago

Probably because of ampersands in the queryString. I'm having the same problem with Google Cloud Storage. Look at https://stackoverflow.com/questions/51946375/ffmpeg-for-aws-s3-bucket-signed-url-not-working-in-node-js for a similar problem. For the record, adding backslashed quotes ("\"" + url + "\"") is not working.

snobu commented 4 years ago

@ocramot Did you ever find a workaround for this issue? I've just hit this bug but with a different URL (still with an ampersand).

ocramot commented 4 years ago

@snobu sorry, I really can't help you. I had a look at our old code and it just seems that we get the signed url using Google Cloud Storage APIs and ffmpeg seems to like it. I don't remember if and how we worked around it.

snobu commented 4 years ago

Thanks for getting back to me. Fixed my problem. It was never the URL but the Authorization header i had to send along. I simply needed to escape the whitespace for some reason 

Authorization:\ Bearer\ value