mirror of
https://git.ffmpeg.org/ffmpeg.git
synced 2025-02-21 22:36:59 +00:00
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 31dfc49598
)
This commit is contained in:
parent
9c96b1efb1
commit
77dafced71
@ -265,6 +265,8 @@ static int process_line(URLContext *h, char *line, int line_count,
|
||||
s->filesize = atoll(slash+1);
|
||||
}
|
||||
h->is_streamed = 0; /* we _can_ in fact seek */
|
||||
} else if (!strcasecmp (tag, "Accept-Ranges") && !strncmp (p, "bytes", 5)) {
|
||||
h->is_streamed = 0;
|
||||
} else if (!strcasecmp (tag, "Transfer-Encoding") && !strncasecmp(p, "chunked", 7)) {
|
||||
s->filesize = -1;
|
||||
s->chunksize = 0;
|
||||
|
Loading…
Reference in New Issue
Block a user