title: Java applet Security Warning checkbox
body: <p>Loading an applet after installing JRE 7 update 55 I get a "Security Warning" dialog.</p>
  
  <p>I check the checkbox for 
  "Do not show this again for this app and web site" and click on "Allow". The applet loads.</p>
  
  <p>![Security Warning window][<a href="http://i.stack.imgur.com/NN2Cx.png%5d" rel="nofollow">http://i.stack.imgur.com/NN2Cx.png]</a></p>
  
  <p>However if i navigate away from the applet and load it again, the dialog comes up again. It is as if it does not remember the checkbox option.</p>
  
  <p>The  Caller-Allowable-Codebase is set to * in the applets manifest file because the app needs to be deployed on any server designated by our client.</p>
  
  <p>Is this a jre u55/u60 bug? or is there something that needs to be done to make that checkbox functional?</p>
  
  <p>Additional information:
  The applet runs with no problem (displaying the warning window just once), I have the problem with repetetive displaying just on one environment. The main difference is, that it runs on Windows Server 2012 R2, IIS 8.5</p>
  
  <p>I have checked the lap file where the choice is saved (in <code>c:\Users\"user_name"\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\</code> search in subfolders for files containing "js.allowed.codebases=") and for other environment I have:</p>
  
  <pre><code>js.allowed.codebases=https//trial.domain.com\:443
  </code></pre>
  
  <p>but for that one problematic, for the first time allowing, it creates the same, and with every other allowing, it saves the same web in the parameter as follows:</p>
  
  <pre><code>js.allowed.codebases=https//trial.domain.com\:443/thttps//trial.domain.com\:443
  </code></pre>
  
  <p>next loop:</p>
  
  <pre><code>js.allowed.codebases=https//trial.domain.com\:443/thttps//trial.domain.com\:443/thttps//trial.domain.com\:443
  </code></pre>
  
  <p>When I put the domain name into the Caller-Allowable-Codebase manifest parameter, the security window does not show up.</p>
  
  <p>And one more thing - when I load the page/applet on localhost (on that server), it works properly. It seems, that the problem could be also connected somehow with the access via domain?</p>
  
  <p>...any idea?</p>
  
  <p>Thanks</p>