178359 - sun.plugin.liveconnect.OriginNotAllowedException: JavaScript is accessing an applet loaded from jre/lib/ext/applet.jar

Status: RESOLVED EXPIRED

(Core :: Security, defect)

Description

[Tom Fukushima]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021104

I have an jar file for a Java applet that is installed into the lib/ext 
directory of the jre.  Trying to access the public methods of the Applet via 
JavaScript produces an OriginNotAllowedException.

OS: Windows XP Prof, V2002, SP1 and Red Hat Linux 8.0
Java: 1.4.1_01

I will attach some files to reproduce:
1) 2) 3) 4) Note the exception.

This defect is similar to 146458, but not quite since there is only one web 
address being used here.

Reproducible: Always

Steps to Reproduce:
1.MyApplet.html - make this page available via a web server so that it can be 
accessed as http://localhost/MyApplet.html or something like that (the problem 
doesn't happen when the page is opened as a local file)
2.Put the MyApplet.jar file into the lib/ext directory of the JRE (e.g., 
c:/J2SDK1.4.1_01/jre/lib/ext).
3.Open http://localhost/MyApplet.html (or whatever is required to open the page 
from step 1).
4. Press the Make Red button.
Actual Results:  
A OriginNotAllowedException is reported in the Java Console.

Expected Results:  
No exception and the screen should have turned red.  You can see the expected 
behavior by putting the MyApplet.jar file in the same directory as the 
MyApplet.html directory; and deleting the MyApplet.jar file from the lib/ext 
directory.

Comment 1

[Tom Fukushima]

Attachment: Required for step 1 of the defect description

Comment 2

[Tom Fukushima]

Attachment: File required for step 2 of the defect

Comment 3

[Tom Fukushima]

Attachment: The source file that was used to create MyApplet.jar

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.