JDK-4097826 : SOCKS support inadequate
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.1.5,1.4.1,1.4.2_05,5.0
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • OS:
    generic,solaris_2.5.1,solaris_2.6,windows_xp generic,solaris_2.5.1,solaris_2.6,windows_xp
  • CPU: generic,x86,sparc
  • Submitted: 1997-12-08
  • Updated: 2017-05-16
  • Resolved: 2003-08-17
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.
Other
5.0 tigerFixed
Related Reports
Duplicate :  
JDK-4894482 - Tiger PIT: Incorrect socks setting will cause JPI/JWS fail to launch Java app
Duplicate :  
JDK-4697272 - HttpClient should fall back to connecting locally if rejected by instProxy
Description
Name: rm29839			Date: 12/08/97


It looks like SOCKS support, at least in the JDK1.1.3,
is supported by settign system properties that
describe the location of the SOCKS proxy.  These
are examined by PlainSocketImpl.java in the JDK
implementation.

This means that if I set these properties, they
will be used for *all* connections that my application
makes, even to my local host.  That's no good.

It would be much better if I could implement some
interface, say, SocksDirector.  If I have a class
that implements this interface, I could tell the
Socket-level code about it, and each time it's
about to make a connection, it could query my class
to see what socks host/port to use for this connection,
if any.
(Review ID: 21381)
======================================================================
###@###.### 10/29/04 18:22 GMT
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b16
17-08-2004
WORK AROUND Name: rm29839 Date: 12/08/97 None that I can see. ======================================================================
17-08-2004
EVALUATION This is a priority for the next feature release. 1.2 is feature complete at this time. benjamin.renaud@Eng 1998-04-14
14-04-1998