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

Stefan Fritsch sf at sfritsch.de
Sat Sep 3 17:23:04 CEST 2011


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 
dev/201109.mbox/%3C4E5EDBA3.1030703 at rowe-clan.net%3E in case you are 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: ranges.diff
Type: text/x-patch
Size: 522 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20110903/af3f9b14/attachment.bin>

More information about the ffmpeg-devel mailing list