aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/arm/dcadsp_neon.S
diff options
context:
space:
mode:
authorStefan Fritsch <sf@sfritsch.de>2011-09-03 22:29:07 +0200
committerMichael Niedermayer <michaelni@gmx.at>2011-09-21 17:56:15 +0200
commit77dafced713f47dc7c356689871b2ba9d8e64f45 (patch)
tree93f9d16949d966de8c2f3843585037a7dde05abd /libavcodec/arm/dcadsp_neon.S
parent9c96b1efb1bb5094edda383b32106bf1bdf9297d (diff)
downloadffmpeg-77dafced713f47dc7c356689871b2ba9d8e64f45.tar.gz
http: Fix decetion of range support in HTTP servers
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. (cherry picked from commit 31dfc4959816aa4637e50c7f79660c75205ef84c)
Diffstat (limited to 'libavcodec/arm/dcadsp_neon.S')
0 files changed, 0 insertions, 0 deletions