Community
Participate
Working Groups
This functionality is available as part of the enhancements made in java.net in 5.0 release. This bug is to investigate how it could be leveraged in core.net API. Currently ProxyManager which handles proxy settings in Eclipse makes them not only available via API but also via System.properties. These properties were the only way to manage proxy configuration in JSE 1.4 and are consumed by protocol handlers while opening connection. This model is not appropriate because any changes are JVM wide and clients can't have customized settings (e.g. proxy turned off) is desired for some reason. Because of this inflexibility some problems surfaced: 1. A problem is to enable making a socket connection which favors HTTP versus SOCKS proxy when both are defined. (Henrich's suggestion, see bug 295030) 2. For SOCKS there isn't a property that allows specifying proxy bypass hosts. See bug 257107, comment 7.
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.
