[Bug 777222] souphttpsrc: redirect uri is never set

Thu Feb 9 23:31:29 UTC 2017

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

Seungha Yang <sh.yang at lge.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sh.yang at lge.com

--- Comment #20 from Seungha Yang <sh.yang at lge.com> ---
Hello all

There is a regression on redirection handling, and seems to be caused by the
commit "souphttpsrc: properly track redirections"

When adaptivedemux is used and also a fragment's uri is redirected, the
connection for original host may not be cleared properly, since the redirection
was handled by souphttpsrc.
At the end, connection count for a host will hit the MAX_CONNS_PER_HOST defined
in libsoup (this causes pipeline stuck).

I'm not sure this is a bug of libsoup, or souphttpsrc though.

Issue can be reprodued using this m3u8.
http://once.unicornmedia.com/now/master/playlist/4236fac6-f0df-4f9a-b9c7-159cfb257618/97255fb8-6105-4caa-9622-de49bba2cd4b/93ebee84-0b53-4671-a4e1-a5c95b083a0d/content.m3u8?UMOPROFILES=hd3000

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