Desc:
it's expected that applet requiesting old JRE won't cause security warning
( "An application would like access to an old version of Java" ) on the second run
if on the first run permission to run with old JRE has been given.
But in fact on the second run we get the same security warning for all cases below:
- for second run in another browser tab
- for applet reloading using "refresh" button
- for complete browser restart and applert rerun
All works as expected in case of javaws application.
"Insecure JRE versions" option is set to "Prompt user before using insecure JRE versions"
it's expected that applet requiesting old JRE won't cause security warning
( "An application would like access to an old version of Java" ) on the second run
if on the first run permission to run with old JRE has been given.
But in fact on the second run we get the same security warning for all cases below:
- for second run in another browser tab
- for applet reloading using "refresh" button
- for complete browser restart and applert rerun
All works as expected in case of javaws application.
"Insecure JRE versions" option is set to "Prompt user before using insecure JRE versions"
- duplicates
-
JDK-7102635 SSV2:"Allow using insecure JRE versions" option doesn't work for non-jnlp based applets in plugin
-
- Closed
-
- relates to
-
JDK-7114614 SSV2: Incorrect JRE is used for non-jnlp multi applets after reload
-
- Resolved
-