Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 349001 - Network Connections Dialog: Proxy bypass: offer bypass in "Native" and "Direct" Active Provider mode
Summary: Network Connections Dialog: Proxy bypass: offer bypass in "Native" and "Direc...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-10 05:19 EDT by Bernhard Merkle CLA
Modified: 2019-11-14 03:52 EST (History)
1 user (show)

See Also:

Attachments
allow proxy bypass also in native and direct mode (11.94 KB, image/png)
2011-06-10 05:19 EDT, Bernhard Merkle CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Merkle CLA 2011-06-10 05:19:05 EDT 
Build Identifier: 

currently "Proxy bypass" is only obeyed in "Active Provider" mode "Manual"

is makes sense to have some proxy bypass exceptions (means entries which are obeyed) also in "Native" and "Direct" mode.

this way, programmers/eclipse users can specify additional hosts, which are e.g. not obeyed by a central/company wide proxy scripts (e.g. in "Native" mode).

please add the possibility also to have proxy bypass in "native" and "direct" mode. they should have higher priority of course.

Reproducible: Always
Comment 1 Bernhard Merkle CLA 2011-06-10 05:19:39 EDT 
Created attachment 197760 [details]
allow proxy bypass also in native and direct mode
Comment 2 Lars Vogel CLA 2019-11-14 03:52:41 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.