[Bug 792664] souphttpsrc: Should send "Range" when offset is 0

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=792664

Jun Xie <jun.xie at samsung.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jun.xie at samsung.com

--- Comment #7 from Jun Xie <jun.xie at samsung.com> ---
(In reply to Paul Kim from comment #5)
> Seek function is not working with LGE TVs because when "Range" field is not
> included in request header, "freevideo served by mod_h264_streaming" file
> header is transferred from serverside. However, when "Range" filed is
> included, "freevideo served by mod_h264_streaming" is not included in the
> mp4 file. Thus, the decoder can`t decode normally. 
> The relevent code of ffmpeg is found
> https://github.com/FFmpeg/FFmpeg/blob/
> cbbb2067341d7c2d98f560f81c6fb103af33a490/libavformat/http.c 
> 
>  // Note: we send this on purpose even when s->off is 0 when we're probing,
>  // since it allows us to detect more reliably if a (non-conforming)
>  // server supports seeking by analysing the reply headers.
>     if (!has_header(s->headers, "\r\nRange: ") && !post && (s->off > 0 ||
> s->end_off || s->seekable == -1)) {
>         len += av_strlcatf(headers + len, sizeof(headers) - len,
>                            "Range: bytes=%"PRIu64"-", s->off);
>         if (s->end_off)
>             len += av_strlcatf(headers + len, sizeof(headers) - len,
>                                "%"PRId64, s->end_off - 1);
>         len += av_strlcpy(headers + len, "\r\n",
>                           sizeof(headers) - len);
>     }

1. ffmpeg use range '0-' to verify if server accepts range GET, if yes,
"Accept-Ranges" is processed and set URLContext->is_streamed to 0, as seekable.
Do we also need similar process in soupsrc?
2. what is exactly behaivor of mod_h264_streaming for non-range GET? is there
any reference there?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.