JDK-6608640 : 6u3: applets and jnlp applications that requires proxy to load cannot be loaded
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u3,6u5
  • Priority: P1
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,windows_xp,windows_vista
  • CPU: generic,x86
  • Submitted: 2007-09-25
  • Updated: 2010-09-17
  • Resolved: 2007-09-26
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
6u3 b05Fixed 7Fixed
Related Reports
Duplicate :  
Description
This actually exposed another more serious problem in my DNS cached applet fix:

6594007: cached applets subject to DNS rebinding

When we write the cache entry to the disk, we do a InetAddress.getByName(hostname) to look up the IP of the codebase host.   In the current implementation, if getByName throws UnknownHostException, the write to cache will fail and the applet cannot be loaded.

We should just catch and ignore the exception instead.

This will happen to machines where proxy is needed to access some special hosts.  (e.g in our lab machines, you can only access Internet via proxy.  So basically now in these lab machines, you cannot load any applets from the internet)

Office machines cannot be used to reproduce this problem, because we now have direct Internet access, and we can access both Intranet and Internet hosts without any proxy.

Comments
EVALUATION the problem can only be reproduced on machines that needs proxy to connect to the internet. to make sure the machine is in such configuration, first check that you need proxy settings in web browser to go to java.sun.com; second, open command prompt to go a "ping java.sun.com", it should fail. here is the lab machine networking settings that can be used to reproduce the problem: Windows IP Configuration Host Name . . . . . . . . . . . . : honkong Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : sfbay.sun.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : sfbay.sun.com Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti on Physical Address. . . . . . . . . : 00-0C-F1-85-2D-55 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 10.5.26.135 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.5.26.1 DNS Servers . . . . . . . . . . . : 129.145.155.32 129.145.155.42 Primary WINS Server . . . . . . . : 129.145.155.130 Secondary WINS Server . . . . . . : 129.145.155.131
25-09-2007

EVALUATION we should ignore the unkownhostexception thrown from getbyname when writing the cache entry
25-09-2007