[MPlayer-dev-eng] [PATCH] Fix interpretation of Accept-Ranges http header to match the RFC

[Alexander Kanavin]

Hi,

currently mplayer determines if a http stream is seekable by looking at the 
presence of "Accept-Ranges: bytes" header. If it's there, mplayer decides 
it's possible to seek by using "Range" requests, and not possible otherwise.

However, HTTP specification sets a different rule:
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)
==============================
       Origin servers that accept byte-range requests MAY send

           Accept-Ranges: bytes

       but are not required to do so. Clients MAY generate byte-range
       requests without having received this header for the resource
       involved. Range units are defined in section 3.12.

       Servers that do not accept any kind of range request for a
       resource MAY send

           Accept-Ranges: none

       to advise the client not to attempt a range request.
========================

So it's possible to seek in the absence of such header, and only 
"Accept-Ranges: none" disables it. Attached patch makes mplayer behaviour 
match the RFC.

By the way, my previous two http patches seem to have fallen through, 
what's the best way to get them reviewed/included?

Thanks,
Alex
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 750_http-seekable.diff
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20080710/03c2036d/attachment.asc>