Description of problem: Current proxy config screen is limited in size and scope. Users do not have much room to see the URL they are inputting, and there is no way to know after putting in the proxy info if it works other than trying to use Subscription Manager. It would be nice if there was a "Test Connection" functionality, so that they could find typos before leaving the screen and hitting errors. I'd also like to see the title of the dialog change from "Advanced Network Config" to something like "Proxy Configuration". As far as I can tell, the only network settings they can alter are proxy related, so I don't see a reason to not include the word proxy in the name. Additional info: Wireframe of new design can be seen at - https://engineering.redhat.com/trac/subscription-manager/attachment/wiki/GUIRedesign/Proxy%20Config.png
Created attachment 576299 [details] Current Dialog
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
commit d12ddfd4ec2089c8be0e32c211bdaa3ee5738063 Refs: <origin/awood/810998>, 810998, subscription-manager-1.0.4-1-39-gd12ddfd Author: Alex Wood <awood> AuthorDate: Thu Jun 14 07:34:36 2012 -0400 Commit: Alex Wood <awood> CommitDate: Tue Jun 26 10:47:25 2012 -0400 810998: Add a button to test a proxy connection. Also change dialog window title.
Created attachment 595056 [details] proxy configuration Tested with: subscription-manager-gui-1.0.5-1.git.31.a3d5de2.el5 The window can be re-sized to view the entirety of your entries, the window has been re-titled to "Proxy Configuration", and the Test Connection button works through happy-path scenarios. Marking VERIFIED.
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-2013-0033.html