From: RichBall <rg...@el...> - 2004-01-03 14:43:46
|
On Sat, 3 Jan 2004 03:36:25 +0100 (CET), Miguel Howard wrote > > I recommend that you use the additional applet attribute > codebase="../myJmolSubdirectory" > or > codebase="somePathToTheJmolApplet" > > Note that this path is the path that will be seen from perspective > of the browser, not from the filename. Actually it seems the restriction is even tighter than this. Quoting from the definition for an applet: codebase = uri This attribute specifies the base URI for the applet. If this attribute is not specified, then it defaults the same base URI as for the current document. Values for this attribute may only refer to subdirectories of the directory containing the current document. Note. While the restriction on subdirectories is a departure from common practice and the HTML 3.2 specification, the HTML Working Group has chosen to leave the restriction in this version of the specification for security reasons. So the only choice is either the same directory as the page or a subdirectory of that directory. This works for the static page but not the cgi-created page. > > I am somewhat concerned that one of the log messages says > /usr/people/web > and the other says > /usr2/people/web > > Not sure why that is ... web server config seems out of whack ... > but that may be a minor issue. Just a cut-paste problem, the "2" isn't really there. > > The primary problem is that you cannot put the JmolApplet.jar in your > cgi-bin directory. > Apparently, as far as an applet is concerned, there is no defined directory for the cgi-created document. So, even though the server is reporting a problem finding the applet code in the cgi-bin directory that isn't really where it needs to find it. I guess I had better reconsider using cgi-generated pages. Rich |