Description of problem: Spice client tries to directly access the target system/VM IP address, even though it is launched via a web page that is currently using a proxy to access the RHEVM. Version-Release number of selected component (if applicable): 3/22/2012 release. How reproducible: always Steps to Reproduce: 1. press console button when connected through a proxy, where direct connect is not allowed. 2. 3. Actual results: client fails to connect, netstat shows attempt to directly connect to ip:5901, where should be connecting through proxy Expected results: spice client should use socks proxy settings or allow them to be set somewhere. Additional info:
This is not a valid request. The browser proxy is for the browser, not for Spice. It's not the same protocol, there is no reason to share the same settings. However, in RHEVM 3.2, the spice client will support a HTTP proxy if the portal/rhevm is confured to use it (or if the environment SPICE_PROXY is set)
(In reply to comment #1) > This is not a valid request. The browser proxy is for the browser, not for > Spice. It's not the same protocol, there is no reason to share the same > settings. > > However, in RHEVM 3.2, the spice client will support a HTTP proxy if the > portal/rhevm is confured to use it (or if the environment SPICE_PROXY is set) marc-andre - i may have missed this, but how can portl pass to spice client proxy details in rhev 3.2 (i.e., is there support in activex/xpi for this)?
(In reply to comment #2) > (In reply to comment #1) > > This is not a valid request. The browser proxy is for the browser, not for > > Spice. It's not the same protocol, there is no reason to share the same > > settings. > > > > However, in RHEVM 3.2, the spice client will support a HTTP proxy if the > > portal/rhevm is confured to use it (or if the environment SPICE_PROXY is set) > > marc-andre - i may have missed this, but how can portl pass to spice client > proxy details in rhev 3.2 (i.e., is there support in activex/xpi for this)? We have added the Proxy property on both spice activex (bug 909496) and xpi (upstream coming 2.9, no bug yet afaik).