Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337552

Summary: [proxy] localhost hostname should be added to proxy exception list
Product: [Eclipse Project] Platform Reporter: Krzysztof Daniel <krzysztof.daniel>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: ericdp, krzysztof.daniel, malgorzata.tomczyk, michael.grosze
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Krzysztof Daniel CLA 2011-02-18 06:18:07 EST

    
Comment 1 DJ Houghton CLA 2011-02-18 14:02:02 EST
I'm not sure but I think this would be in the Team preferences. Moving to Platform/Team for comment.

Please enter real content in future bug reports. The summary is an editable field and can be over-written and the original contents only available from the bug history view, which can make it difficult. 
   https://bugs.eclipse.org/bugs/bugwritinghelp.html
Thanks.
Comment 2 Eric Peters CLA 2011-04-01 13:24:52 EDT
Hi, any update on this one? An adopter product is looking for this change.
Comment 3 Michael Große CLA 2011-09-02 09:56:21 EDT
Do you have any news on this bug?

The goal is to add the host name of the machine to the HTTP proxy exception list in the preferences. Thereby HTTP clients connecting to the machine itself would not connect via the HTTP proxy and thus communication would not fail.

If host name would be automatically added to the HTTP proxy exception list, the user would not need to set this manually in each new workspace.
Comment 4 Malgorzata Janczarska CLA 2011-09-05 05:55:30 EDT
"localhost" and "127.0.0.1" are added to proxy bypass by default. They may be added without any additional actions.
The problem with host name is that it may be changed anytime, so we would have to do the system check every time workspace is loaded. In most of those checks we would learn that there's no action to be performed. And what if the hostname would change? Shall we remove the previous one or leave it? How would we know what was the previous hostname? We would have to add some API to mark it.
Comment 5 Lars Vogel CLA 2019-11-14 03:08:21 EST
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.