Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an Oracle Application server that has been upgraded. It serves users a java file which they launch in their browser. After the upgrade user's browsers are still pulling the old java file from their local cache and receiving an error. If a user clears their java cache things will work correctly.

There has got to be a way to tell clients that they need to get the new java file rather then using their local cached version.

share|improve this question
Relevant:… – iainlbc Jan 27 '12 at 1:33
up vote 3 down vote accepted

The algorithm for Java applet caching is described here.

Try getting Apache to return reasonable Last-Modified headers. If this is not happening, this could mess up the caching algorithm. Last-Modified should be a later date than the previous applet.

Also check that the MIME type for the JAR files from Apache are application/java-archive, as not having this can mess up caching (but usually this prevents them from being cached).

There is also the option of making changes to the HTML files as described.

share|improve this answer

Are you able to change the link that users click to open the java file? If so, there are a couple of ways to fix it there:

  • change appname.jar to appname.jar?version=20120124.
  • add <param name="cache_option" value="no"> between <object> and </object>. (This will cause clients to reload the latest version every time, not just once.)
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.