JDK-8029138 : Esl not working when permissions attribute not in manifest
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7u51
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2013-11-25
  • Updated: 2014-02-13
  • Resolved: 2014-02-13
Related Reports
Duplicate :  
JDK-8029135 - ESL not working for JNLP applications without an href
Description
         
SHORT SUMMARY:
esl not working when permissions attribute not in manifest
DESCRIPTION:
The working direction for Exception Site List functionality in 7u51 is to
support JARs that are missing the Permissions attribute in the manifest.

We tested, and cannot get one of our older JARs (that is missing the
Permissions Attribute) to run, no matter how we configure the ESL:

http://a.b.c.d
http://a.b.c.d/
http://a.b.c.d:80
http://a.b.c.d:80/

Using High or Very High security level. Using "Medium" allows the JAR to run
without any ESL configuration.

These JARs are embedded in Oracle servers and can't just be resigned and
updated. We are counting on ESL to allow existing deployed servers to still
function.
Comments
The problem here is the jnlp file does not have an href. If a jnlp application is launched normally (ie: by clicking on a jnlp file link in a browser) and it does not have an href to it's jnlp file, we cannot know where the jnlp file came from. In that case we cannot match an ESL location or a location based DRS rule. This is internally documented at: http://wiki.se.oracle.com/display/JPGC/Exception+Site+List but does not seem to be documented in the release notes. you can fix app by adding an href to the main jnlp file (in the jnlp file)
02-12-2013
duplicate of JDK-8029135
26-11-2013