On 07/08/2011 05:21 PM, Reinhold Störmann wrote: > Am 08.07.2011 16:34, schrieb Rolf Huehne: >> On 07/08/2011 04:04 PM, Reinhold Störmann wrote: >>> Lets try to sort thesee things out correctly: >>> >>> 2. How can I verify that the signed applet is running and not the unsigned? >>> >> There are several indicators: >> >> 1) The first time you start the applet from a specific source there >> should pop up a security warning dialog. If you accept running the >> signed applet there it should run as a signed applet. If you don't >> accept it will still run but only like the unsigned applet. >> >> 2) The usual "Jmol" text at the bottom right of the applet frame (called >> "frank" within Jmol for some historical reason) is changed to a red >> "Jmol_S". >> >> 3) If you open the applet menu (e.g. with right-click) and go to "About >> Jmol" (or maybe it's translation to another language) then it is >> indicated behind the jmol version number: >> Jmol 11.6.8 (signed) >> >> (The "About Jmol" menu part changed in newer versions a little but I >> would expect that this information will still be there). >> >> You can try running the signed applet from this URL: >> http://www.imb-jena.de/cgi-bin/3d_mapping.pl?CODE=1deh&APPLET=signed > This url really starts the signed applet. >> There I invoke it explicitly: >> jmolInitialize("/ImgLibPDB/jmol/jmol-11.6.8", "JmolAppletSigned0.jar"); > I changed my code to invoke the signed applet explicityl as you did, but > still the unsigned applet is loaded. > Cannot figure out why. > > Closed all browser windows, and started the browser anew to remove > possible browser cache effects, still > > jmolInitialize(\"external/jmol\",\"JmolAppletSigned0.jar\") > > seems to load the unsigned applet. > > > Here is the content of the java console: > >> Java Plug-in 1.6.0_25 >> Verwendung der JRE-Version 1.6.0_25-b06 Java HotSpot(TM) Client VM <snip> > basic: Fortschritts-Listener hinzugefügt: >> sun.plugin.util.GrayBoxPainter$GrayBoxProgressListener@1d05c81 >> basic: Plugin2ClassLoader.addURL parent called for >> http://localhost/local/fernandez/external/jmol/JmolApplet0.jar >> security: Blacklist-Revocation-Check ist aktiviert. >> security: Die Überprüfung der Liste vertrauenswürdiger Bibliotheken >> ist aktiviert >> network: Cache-Eintrag gefunden [url: >> http://localhost/local/fernandez/external/jmol/JmolApplet0.jar, >> Version: null] prevalidated=false/0 >> network: Verbindung von >> http://localhost/local/fernandez/external/jmol/JmolApplet0.jar mit >> Proxy=DIRECT wird hergestellt >> network: Verbindung von http://localhost:80/ mit Proxy=DIRECT wird >> hergestellt >> network: ResponseCode für >> http://localhost/local/fernandez/external/jmol/JmolApplet0.jar: 304 >>
From the Java log snippet above it seems to me that your changed page was not loaded but rather an older version because it only tried to open 'JmolApplet0.jar' and not 'JmolAppletsigned0.jar'. So it still seems to be in a cache. What code is dispayed if you display the HTML source code in your browser? Maybe you should change the page name to a name you never used before to avoid any cache problem. I wouldn't think that the problem is the Java cache here because the signed applet wasn't even tried according to the Java console output. Have you tried different browsers? Regards, Rolf ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
