[Webkit-unassigned] [Bug 115353] Add support to disable "Accept-Encoding:" HTTP header on soup ResourceRequest

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=115353





--- Comment #3 from Andre Moreira Magalhaes <andrunko at gmail.com>  2013-04-29 10:25:44 PST ---
What happens here is that:
1 - If we don't set the size on gst appsrc (set to -1), it will break seek and consider the stream a live stream
2 - if we set the wrong size (in case the content-length has the compressed size opposed to the actual size), gst will consider EOF before the stream ends

We could probably indeed set the size to -1 by checking this flag you mentioned, but seek would be broken for all servers returning compressed data.(In reply to comment #2)
> (In reply to comment #0)
> > This is especially needed by the webkit gstreamer source element which needs to rely on the correct data size to download streams.
> 
> That seems improbable... what do you do if there's no Content-Length header at all?
> 
> I think the problem is just that the gstreamer source needs to know to not look at the declared Content-Length if the SOUP_MESSAGE_CONTENT_DECODED flag is set.

What happens here is that:
1 - If we don't set the size on gst appsrc (set to -1), it will break seek and consider the stream a live stream
2 - if we set the wrong size (in case the content-length has the compressed size opposed to the actual size), gst will consider EOF before the stream ends

We could probably indeed set the size to -1 by checking this flag you mentioned, but seek would be "broken" (disabled) for all servers returning compressed data.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.