Community
Participate
Working Groups
Build Identifier: 3.4.2 M20090211-1700 If a manual proxy configuration is specified in the Network Connections preferences page, this appears to be stored in the workspace and always used no matter which configuration the user chooses. Monitoring of the network traffic show the proxy server is being used in place of the direct connection requested. Using Restore Defaults clears the proxy from the Network Connections page but it is still remembered and used. Only work around I have found is to remove proxyData entries from org.eclipse.core.net.prefs and restart eclipse. The following appears in the .log: !ENTRY org.eclipse.core.net 1 0 2010-05-25 17:07:42.421 !MESSAGE System property http.proxyHost has been set to aaaaaa.bbbbbb.ccccc.com by an external source. This value will be overwritten using the values from the preferences !ENTRY org.eclipse.core.net 1 0 2010-05-25 17:07:42.437 !MESSAGE System property http.proxyPort has been set to 8888 by an external source. This value will be overwritten using the values from the preferences Reproducible: Always Steps to Reproduce: 1.Define a manual proxy configuration. 2.Choose Direct connection. 3.Try a Software update for The Eclipse Project Updates Result expected is that the eclipse site download.eclipse.org appears in the connections log of a monitoring tool or firewall e.g. I used Symantec Client Firewall Log Viewer for Connections. Actual result is that the proxy server appears in the log instead, indicating it is still being used for connections.
Mark, Can you still recreate this issue? Have you checked the same steps in Eclipse 3.6? I cannot reprodue you issue on Eclipse 3.4.2, 3.5 and 3.6.
(In reply to comment #1) > Mark, > Can you still recreate this issue? Have you checked the same steps in Eclipse > 3.6? I cannot reprodue you issue on Eclipse 3.4.2, 3.5 and 3.6. I believe we've seen a user recreate the same problem. That is, If you have a SYSTEM proxy set in Windows, every time you start up, the proxy is inherited from Windows again, even if you cleared it last time.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
