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.
Unified · Split
| @@ -265,6 +265,8 @@ static int process_line(URLContext *h, char *line, int line_count, · 264 unmodified lines | |||
| 265 | s->filesize = atoll(slash+1); | 265 | s->filesize = atoll(slash+1); |
| 266 | } | 266 | } |
| 267 | h->is_streamed = 0; /* we _can_ in fact seek */ | 267 | h->is_streamed = 0; /* we _can_ in fact seek */ |
| 268 | } else if (!strcasecmp (tag, "Accept-Ranges") && !strncmp (p, "bytes", 5)) { | ||
| 269 | h->is_streamed = 0; | ||
| 268 | } else if (!strcasecmp (tag, "Transfer-Encoding") && !strncasecmp(p, "chunked", 7)) { | 270 | } else if (!strcasecmp (tag, "Transfer-Encoding") && !strncasecmp(p, "chunked", 7)) { |
| 269 | s->filesize = -1; | 271 | s->filesize = -1; |
| 270 | s->chunksize = 0; | 272 | s->chunksize = 0; |