JDK-5001942 : Missings SOCKS support for direct connections
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.4.2_03
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: linux_redhat_9.0
  • CPU: x86
  • Submitted: 2004-02-24
  • Updated: 2013-08-07
  • Resolved: 2013-04-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8 b86Fixed
Java application behind firewalll with SOCKS proxy cannot make connection to both external world and internal world (depends on SOCKS server settings). There is missing possibility similar to http and ftp protocol network properties that allow to define proxy and target hosts that should not use such proxy.

Expected is exiting and documented socksNoProxyHost property.
###@###.### 2004-02-24

SQE verified

This issue came up on openjdk mailing lists, cross post: http://mail.openjdk.java.net/pipermail/net-dev/2013-March/005921.html http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-March/015470.html

WORK AROUND System.setProperty("socksProxyHost", null); socket.connect(); System.setProperty("socksProxyHost", "icsocks...");

EVALUATION This is partially fixed in Tiger. The new ProxySelector mechanism provides ways to do just that even though the SocksNoProxyHosts property is not there. Also, if java.net.useSystemProxies is set to true, then on Windows & Gnome systems, the exclude list do affect Socks proxying. Still it would be nice to provide a default cross platform way to do this as well, but this is will be in a later release. ###@###.### 2004-02-24