MPM does not utilize proxies!!

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Work in an office that requires a proxy to get out
2. Try to use MPM...
3. It won't connect!  It seems MPM doesn't use proxies, depends on having a 
direct connection...?

What is the expected output? What do you see instead?

I would assume that if my proxy settings are correct, it would connect.  At 
first I thought it was my work policies (blocking the traffic) but I recently 
setup an ssh tunnel @ work to my home PC, just to see - and MPM still does not 
connect to my home box.

This worked for a brief period at work when our proxy servers were down and 
everyone essentially had an open internet connection ;).

What version are you using? On what operating system?
Music Player Minion: 2.1.1
Firefox: 4.0.1
Music player Daemon (MPD): 0.17.0
OS: Ubuntu 10.04.2

Please provide any additional information below.

I am not sure of a way to independently verify, but it seems that MPM certainly 
depends on an open cxn, it does not respect proxies.  I use FoxyProxy to switch 
proxies depending on what site I'm going to, and I see nothing triggered when I 
first open FF and try to get MPM to connect...

Original issue reported on code.google.com by arrrg...@gmail.com on 18 May 2011 at 3:31

[GoogleCodeExporter]

Hi

I will have a look to your issue as soon as the extension is available fr 
Firefox 5.0
Though, due to the nature of Music Player Daemon protocol, it is unlikely that 
your proxy may support it.

Original comment by aurelien...@gmail.com on 31 Jul 2011 at 4:57

[GoogleCodeExporter]

Thanks for looking into the issue.

I'm curious, does MPM support any proxy, or does it indeed depend on an open 
connection to the internet...?

Original comment by arrrg...@gmail.com on 31 Jul 2011 at 4:59

[GoogleCodeExporter]

MPM as of Firefox 3.6 is know to support proxy to retrive album covers. this 
feature uses the "normal" way to retrieve content.
Though, for the connection with MPD, it's a direct TCP connection (like 
telnet). and then the commands are pushed, but the format of the protocol is 
far far from anything related to http.
It might be possible to use a proxy via the "CONNET" method, but this will 
require some extra development.

I'm setting your issue as enhancement. 

For now, all my focus is on ff5 compatibility as ff6 is already on its way.

Original comment by aurelien...@gmail.com on 31 Jul 2011 at 5:58

• Added labels: Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Certainly an enhancement, and I would certainly prefer you focus on FF 
compatibility.

Thanks for explaining basically how the connection works.  I realize now that 
it's not an easy fix.  I appreciate the effort!

Original comment by arrrg...@gmail.com on 1 Aug 2011 at 4:57