[FFmpeg-devel] [PATCH] avformat/http: allow content range to set filesize

[Aman Gupta]

On Tue, Jan 31, 2017 at 2:26 AM, Philip de Nier <philipn at rd.bbc.co.uk>
wrote:

> On 09/12/2016 11:54, PHILIP DE NIER wrote:
> > Hi,
> > Attached patch fixes issue #6007 for me.
> > I think it could improved / extended because the "if (s->seekable ==
> > -1 && (!s->is_akamai || s->content_range_len != 2147483647))" is
> > probably better placed http_read_header along with the similar
> > is_mediagateway workaround. I wasn't sure whether the is_akamai should
> > only be triggered if the filesize was read from the Content-Range header.
> > Philip
> >
> >
> >
> > _______________________________________________
> > ffmpeg-devel mailing list
> > ffmpeg-devel at ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >
>
> Ping?
>
> A summary of issue #6007:
> A quicktime file is being served using chunked transfer and byte range
> requests enabled. FFmpeg opens the file in libavformat, mov.c
> mov_read_default and it fails to complete because the (seekable) file
> returns an error (ENOSYS) for avio_size. avio_size is returning an error
> because the code in libavformat/http.c is ignoring the resource length
> provided by the Content-Range response header.
>

This looks reasonable to me. Any thoughts Anssi?

Aman


>
> Thanks.
> Philip
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>