JDK-6887492 : REGRESSION:proxy automatic configuration does not work since 6u14
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u14,6u15,6u16,6u20
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_10,windows_xp,windows_vista
  • CPU: generic,unknown,x86
  • Submitted: 2009-10-01
  • Updated: 2012-10-10
  • Resolved: 2010-03-03
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.
JDK 6 JDK 7
6u18-rev b09Fixed 7Fixed
Related Reports
Duplicate :  
JDK-6960680 - problem with jdk 1.6.0_13 and later and proxy.pac
Duplicate :  
JDK-2184835 - java plugin isInNet return incorrect value
Duplicate :  
JDK-6880340 - java plugin isInNet return incorrect value
Duplicate :  
JDK-6880306 - Proxy.pac script is bad parsed since JRE 6u15
Relates :  
JDK-6922370 - REGRESSION:proxy automatic configuration does not work
Relates :  
JDK-6789865 - Java Plugin isInNet implementation returns incorrect value in some cases
Description
J2SE Version (please include all output from java -version flag):
Java Plug-in 1.6.0_16
Using JRE version 1.6.0_16-b01 Java HotSpot(TM) Client VM
User home directory = D:\Documents and Settings\Administrator

Does this problem occur on J2SE 1.4.x or 5.0.x or 6.0?  Yes / No (pick one)
NO, it works fine with 6u13


Operating System Configuration Information (be specific):
Browser: Internet Explorer 6.0.2900.2180 service pack 2
OS: Windows XP service pack 2


Hardware: Intel CPU

 

Bug Description:
Applets having problem to load properly with latest versions of Java Plugin(6u14, 15 and 16). No problems with early versions of JDK 6.0 are being seen.


found that it has a problem with the proxy automatic configuration script.  If a specific proxy server is entered, there is no issue with that JRE. JRE 6 update 
13 and it did not have a problem with the proxy automatic configuration script.
Looks like something broke in the Sun JRE starting at version 6 update 14.

Attached are the logs.
Comments
EVALUATION This regression is caused due to fix for CR 6789865
19-01-2010
EVALUATION It looks like an issue in JRE for parsing isInNet call: point to my test proxy file in IE browser: http://eltanin.east.sun.com:8000/dennis/bug/dolphin/6.0update/6887492/x.pac Running the test applet in IE browser using JRE 6u18: http://java.sun.com/products/plugin/1.5.0/demos/applets/MoleculeViewer/example1.html You will noticed it using proxy: wrong-proxy.east.sun.com:8080 Now install JRE 6u13 in your machine, running the same applet, you will noticed it using proxy: correct-proxy.east.sun.com:8080 As it state in the bug report, it looks like this bug is introduced in JRE 6u14.
12-01-2010
EVALUATION Customer tried 6u14 b01 and they still see the issue. I am adding Dennis to get some feedback
14-10-2009
EVALUATION This could be related due to fix for CR 6796470 Use new NPAPI entry points for cookie, proxy and browser authenticator access Can customer provide us test case. Also can they try 6u14 b01, as putback for this bug was done in 6u14 b02. Thanks.
13-10-2009