Update 3: When using Fiddler 4 or Charles as a proxy for Internet Explorer and capturing traffic between the server and the browser, the applet loads and works as expected. I've even tried signing the applet using Java 8 Update 172 without altering curity to remove 3DES_EDE_CBC and using that version the ClassNotFoundException still persists as expected. Update 2: I'm also aware that the 3DES Cipher Suites have been disabled in the update to 171 and 172, but the current digest algorithm is SHA-256 and the signature algorithm is SHA256withRSA with a 2048-bit key, which matches the signing certificate's signature algorithm and key.
Update 1: I'm aware that applets are deprecated in Java 9 and that applets don't work in Firefox and Chrome, but this is in Internet Explorer. When clearing the Application cache in the Java configuration, the applet's JAR file doesn't appear again in the cache.Īre you aware of any changes in Java 8u171 or 172 that affect applets? Do you have any suggestions to resolve this?
Using Java 8 update 162 and older is still working on another PC. There aren't any exceptions in the Exception Site List and adding an exception for this site (it worked fine without one on Java 8u162) still displays the exception. The applet is signed with a certificate that is trusted and still valid. I'm using Windows 10 Pro version 1709 build 16299.371. I don't see any reason for this in the 171 or 172 release notes or the 171 or 172 bug fixes. When removing Java 8 update 162 and install Java 8 update 171 or 172, the applet errors with ClassNotFoundException referencing the class listed in the code attribute of the applet tag. When using Java 8 update 162 and older in Internet Explorer, the applet loads and works as expected.
0 kommentar(er)
