So, your next move might be make sure you have the latest version of ffmpeg. What I have observed above (that essentially it is working, perhaps with a small command change) was with a fairly recent version: ffmpeg version 2.8.1 Copyright (c) 2000-2015 the FFmpeg developersīuilt with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04)Ĭonfiguration: -enable-libx264 -enable-gpl -prefix=/usr/local -enable-shared -cc='gcc -fPIC' There are lots of discussions around headers bugs in trac for ffmpeg. But there is an option -user-agent to ffmpeg, and when I replaced -headers "User-Agent: " with -user-agent "", I then did see it too on the server, alongside the X-Forwarded-For header: User-Agent: Mozilla/5.0 (Windows NT 6.1 WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/.80 Safari/537.36 So it looks like ffmpeg is setting it's own.
On the server, I saw: User-Agent: Lavf/56.40.101 matched as AVOption 'headers' with argument 'X-Forwarded-For: 13.14.15.66'. matched as AVOption 'headers' with argument 'User-Agent: Mozilla/5.0 (Windows NT 6.1 WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/.80 Safari/537.36'. When I do this, I see the following relevant output from ffmpeg: Reading option '-headers'. With that running, this enabled me to run your command like: ffmpeg \ nd_error(404,'File Not Found: %s' % self.path) Longer Answerįor debugging, I setup a BaseHTTPSever running at 127.0.0.1:8080 with do_GET() as: def do_GET(self): Make sure you're using the latest ffmpeg, and use the -user-agent option.
0 kommentar(er)
