xine does not use HTTP proxy for MMS MRLs

Bug #64641 reported by Reinhard Tartler on 2006-10-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xine-lib
Confirmed
Medium
xine-lib (Debian)
Confirmed
Unknown
xine-lib (Ubuntu)
Undecided
Unassigned

Bug Description

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.

reassign 278982 xine-lib

thanks.

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

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) wrote :

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.

Changed in xine-lib:
status: Unconfirmed → Confirmed
Changed in xine-lib:
status: Unknown → Confirmed
Changed in xine-lib:
status: Confirmed → Triaged

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.

Changed in xine-lib:
status: Unknown → Confirmed
Changed in xine-lib:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.