-
Bug
-
Resolution: Fixed
-
P3
-
6, 6u10
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2199225 | 7 | Calvin Cheung | P3 | Resolved | Fixed | b64 |
JDK-2161238 | 6u7 | Calvin Cheung | P3 | Closed | Won't Fix |
The Java Plug-In for Firefox in 1.6.0_03 introduced a regression where calls in from JavaScript via LiveConnect which cause network connections to be initiated fail with AccessControlExceptions.
The thread on the Java Plug-In forum on java.sun.com describing the problem, in particular a link to a test case, is http://forum.java.sun.com/thread.jspa?threadID=5230759&start=30 -- look for the posting by Cyrille linking to http://oueb.org/AppletFireFoxLiveconnectBug.html . A copy of this test case will be made internally and described in the Comments section.
The problem appears to be that some code in the Java Plug-In resolves hostnames to IP addresses where it used to be naming the host symbolically. Access control checks are failing because on one side we have the symbolic host name and on the other side its IP address, and the security checks do not understand that these are equivalent.
Note that we copied this test case in house and it does not fail when hosted on our internal servers. The issue appears to be related to how name service lookups work for the particular host.
The thread on the Java Plug-In forum on java.sun.com describing the problem, in particular a link to a test case, is http://forum.java.sun.com/thread.jspa?threadID=5230759&start=30 -- look for the posting by Cyrille linking to http://oueb.org/AppletFireFoxLiveconnectBug.html . A copy of this test case will be made internally and described in the Comments section.
The problem appears to be that some code in the Java Plug-In resolves hostnames to IP addresses where it used to be naming the host symbolically. Access control checks are failing because on one side we have the symbolic host name and on the other side its IP address, and the security checks do not understand that these are equivalent.
Note that we copied this test case in house and it does not fail when hosted on our internal servers. The issue appears to be related to how name service lookups work for the particular host.
- backported by
-
JDK-2199225 Regression: AccessControlExceptions introduced in 1.6.0_03 on Firefox during LiveConnect calls
- Resolved
-
JDK-2161238 Regression: AccessControlExceptions introduced in 1.6.0_03 on Firefox during LiveConnect calls
- Closed
- duplicates
-
JDK-6622150 Applet no longer able to connect to originating host in 1.6.0_03 with Firefox
- Closed