JDK-4480339 : RFE: Java Plug-in should try all proxies returned by auto-proxy script
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.3.0,1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2001-07-16
  • Updated: 2002-04-13
  • Resolved: 2002-04-08
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
1.4.1 hopperFixed
Related Reports
Duplicate :  
JDK-4523220 - RFE: Multiple proxy retry
Relates :  
JDK-6816935 - .pac fails with 5.0
Description

Name: mt13159			Date: 07/16/2001


In the Java plug-in proxy document at:
http://java.sun.com/products/plugin/1.3/docs/proxies.html
it says:
"the function FindProxyForURL always returns proxy information as a string. Java Plug-in extracts the setting in the following way...If 'PROXY' is in the string, it uses the first proxy setting for the connection."
However, as described in the Netscape auto-proxy documentation at:
http://devedge.netscape.com/docs/manuals/proxy/adminnt/autoconf.htm
the return value of FindProxyForURL is a list of entries separated by semicolons.  If the first proxy in the list cannot be contacted, the next one should be used.
We are requesting that the plug-in implement the same behavior.  That is, if the attempt to contact the first proxy fails, the next proxy in the list should be used, and so on.  We have customers that require this behavior.
(Review ID: 128073) 
======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: hopper FIXED IN: hopper INTEGRATED IN: hopper VERIFIED IN: hopper-beta
14-06-2004
EVALUATION This is a nice to have feature. Will take it as requirement for tiger. stanley.ho@Eng 2001-07-16 I am in progress of fixing this bug. Stanley suggested to make this feature available for all the other proxy configuration mechanism. However, I think it is not appropriate to do this. Two reasons: 1. Make the proxy configuration mechanism complicated 2. Performance will be degraded. For manual configuartion, if the proxy is down or has been reset, we can not do much unless the user hit "p" to reload the proxy. Otherwise, we need to do check everytime we made a connection. For autoproxy configuartion, it makes sense because anyway we need to get proxy everytime from the return value of "FineProxyForURL()". So the RFE will only include the fix for autoproxy configuration. ###@###.### 2002-03-01
01-03-2002