[FFmpeg-user] http hangs, https not, following ubuntu build from scratch.
jim at vsiwest.com
Tue Mar 19 15:17:03 EET 2019
> Immediate exit requested
this was me hitting ctrl-c
it is not impossible that the corporate network is acting with prejudice.
I didnt see similar bugs by googling so i asked here. if there's no
obvious build switches to reference then I am OK sticking with curl for
now, or wget -c ahead of time. bash pipes aren't currently a project
risk, but if this were AWS lambda or google's function hosting ffmpeg the
builtin protocol becomes a lot more serious.
On Tue, Mar 19, 2019 at 8:01 PM Moritz Barsnick <barsnick at gmx.net> wrote:
> On Tue, Mar 19, 2019 at 16:28:48 +0700, James Northrup wrote:
> > I have been having to wrap http in -i <( curl URL) using head ffmpeg on
> > ubuntu 19
> > i want to know if there is a configure switch i might've used that
> > a situation where http is buggered. i have two such ubuntu 19 machines
> > with similar results.
> This is your own built binary? You could try a binary from
> https://johnvansickle.com/ffmpeg/ for comparison.
> It can't be an ffmpeg issue, https uses mostly the same code as http,
> except for establishing the connection.
> > Immediate exit requested
> I don't know which code causes this, perhaps there's more insight from
> "-loglevel debug".
> Since you write that curl works, I would guess that a semi-transparent
> proxy is choking on ffmpeg's implementation of the protocol, but not
> curl's? Or the server's HTTP port doesn't like your source address. Or
> something similarly stupid. A tcpdump/Wireshark trace might be
> interesting. But try a different binary first please.
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user