Description of problem: Usual way people define value for http proxy, like http_proxy env variable read by many many cli tools on Linux, is in the way: * http://fqdn:port or * http://fqdn:port/ (fqdn can be replaced by resolvable name or with an IP) Anyway, virt-viewer does _NOT_ use http proxy when it gets spice proxy value with trailing '/'. This is very annoying. Version-Release number of selected component (if applicable): sf18 - 0.5.3 How reproducible: 100% Steps to Reproduce: 1. have SpiceProxyDefault without trailing '/' 2. open console 3. have SpiceProxyDefault with trailing '/' 4. open console Actual results: 4. does not even try to use proxy, it just uses direct connection Expected results: work as many other apps/tools Additional info:
I wonder if there is any spec for this... Anyway, here is the patch: http://lists.freedesktop.org/archives/spice-devel/2013-June/013679.html
confirmed on mingw-virt-viewer-0.5.3-28 -> qa_ack+
This bug is currently attached to errata RHEA-2013:15512. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0034.html