Browse Source

lavf/http: handle case where the server returns a redirect during a seek

txoffer (e.g. http://tori.aoi-chan.com/ ) redirects to the same URI on your
first request, and serves the actual file on the second. It's stupid, but AFAIK
technically compliant. We'd previously see the server not handing back a Range
header and return an error; now, instead, we see that there's a redirect and
keep track of the offset we want while trying again at the new URL.

Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
tags/n2.7
Rodger Combs Michael Niedermayer 11 years ago
parent
commit
a4d58c97d0
1 changed files with 3 additions and 0 deletions
  1. +3
    -0
      libavformat/http.c

+ 3
- 0
libavformat/http.c View File

@@ -917,6 +917,9 @@ static int http_connect(URLContext *h, const char *path, const char *local_path,
if (err < 0)
goto done;

if (*new_location)
s->off = off;

err = (off == s->off) ? 0 : -1;
done:
av_freep(&authstr);


Loading…
Cancel
Save