Re: [FFmpeg-devel] [PATCH] http: Check for AVERROR_EOF in the check for premature end

2020-11-20 Thread Martin Storsjö
On Fri, 20 Nov 2020, Jan Ekström wrote: On Fri, Nov 13, 2020 at 12:17 AM Martin Storsjö wrote: When the check was added (in 3668701f9600, in 2015), some IO functions returned 0 on EOF (in particular, the TCP protocol did, but the TLS protocol returned AVERROR_EOF). Since 0e1f771d2200d in 2017

Re: [FFmpeg-devel] [PATCH] http: Check for AVERROR_EOF in the check for premature end

2020-11-19 Thread Jan Ekström
On Fri, Nov 13, 2020 at 12:17 AM Martin Storsjö wrote: > > When the check was added (in 3668701f9600, in 2015), some IO > functions returned 0 on EOF (in particular, the TCP protocol > did, but the TLS protocol returned AVERROR_EOF). Since > 0e1f771d2200d in 2017, the TCP protocol also returns AVE

Re: [FFmpeg-devel] [PATCH] http: Check for AVERROR_EOF in the check for premature end

2020-11-17 Thread Martin Storsjö
On Fri, 13 Nov 2020, Martin Storsjö wrote: When the check was added (in 3668701f9600, in 2015), some IO functions returned 0 on EOF (in particular, the TCP protocol did, but the TLS protocol returned AVERROR_EOF). Since 0e1f771d2200d in 2017, the TCP protocol also returns AVERROR_EOF instead of

[FFmpeg-devel] [PATCH] http: Check for AVERROR_EOF in the check for premature end

2020-11-12 Thread Martin Storsjö
When the check was added (in 3668701f9600, in 2015), some IO functions returned 0 on EOF (in particular, the TCP protocol did, but the TLS protocol returned AVERROR_EOF). Since 0e1f771d2200d in 2017, the TCP protocol also returns AVERROR_EOF instead of 0, making the check for premature end never ha