[FFmpeg-devel] [PATCH] libavformat: Fix decetion of range support in HTTP servers

Michael Niedermayer michaelni at gmx.at
Sat Sep 3 22:31:26 CEST 2011

On Sat, Sep 03, 2011 at 05:23:04PM +0200, Stefan Fritsch wrote:
> Hi,
> currently libavformat only allows seeking if a request with "Range: 
> 0-" results in a 206 reply from the HTTP server which includes a 
> Content-Range header. But according to RFC 2616, the server may also 
> reply with a normal 200 reply (which is more efficient for a request 
> for the whole file). In fact Apache HTTPD 2.2.20 has changed the 
> behaviour in this way and it looks like this change will be kept in 
> future versions. The fix for libavformat is easy: Also look at the 
> Accept-Ranges header.
> There is some discussion at 
> http://mail-archives.apache.org/mod_mbox/httpd-
> dev/201109.mbox/%3C4E5EDBA3.1030703 at rowe-clan.net%3E in case you are 
> interested.

patch applied, thanks


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In fact, the RIAA has been known to suggest that students drop out
of college or go to community college in order to be able to afford
settlements. -- The RIAA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20110903/37352cc3/attachment.asc>

More information about the ffmpeg-devel mailing list