xine does not use HTTP proxy for MMS MRLs

[Reinhard Tartler]

When accessing a MMS MRL, xine tries first to connect to server on TCP
port 1750. If that fails, it falls back to HTTP, but without using the
proxy given in the configuration file. This makes it impossible to
access these MRLs if TCP port 80 has been blocked for outgoing traffic.

[Siggi Langauf (langausd)]

reassign 278982 xine-lib

thanks.

Actually, it's libxine's mms plugin that does the connection to the MMS
server...

[LENHOF Jean-Yves (jean-yves)]

Hi,

Just want to confirm this problem with the current version...
..
Source: xine-lib
Version: 1.0.1-1
.

Regards,

--
Jean-Yves LENHOF

[Reinhard Tartler (siretart)]

# Automatically generated email from bts, devscripts version 2.9.10
forwarded 278982 http://sourceforge.net/tracker/index.php?func=detail&aid=1438571&group_id=9655&atid=109655

[Reinhard Tartler (siretart)]

When accessing a MMS MRL, xine tries first to connect to server on TCP
port 1750. If that fails, it falls back to HTTP, but without using the
proxy given in the configuration file. This makes it impossible to
access these MRLs if TCP port 80 has been blocked for outgoing traffic.

[Reinhard Tartler (siretart)]

Forwarded bug from
https://bugs.edge.launchpad.net/ubuntu/+source/xine-lib/+bug/64641

When accessing a MMS MRL, xine tries first to connect to server on TCP
port 1750. If that fails, it falls back to HTTP, but without using the
proxy given in the configuration file. This makes it impossible to
access these MRLs if TCP port 80 has been blocked for outgoing traffic.