File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JNLP and Web Start and the fly likes IE & JNLP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » JNLP and Web Start
Bookmark "IE & JNLP" Watch "IE & JNLP" New topic


Cristian Negresco
Ranch Hand

Joined: Sep 15, 2001
Posts: 182

An application is lauched through a jnlp file. Now the problem is that the browser uses a previously cached vrsion of the file insted to retrieve a new one.

- the jnlp deployed on WebShpere.
- offline is not allowed in the jnlp file, but this has to do with the JWS cache only.
- there is a ServletFilter which sets the "expires" header, and/or the max-age together with forcing of the refresh. I tried here all the combinations possible I think...
- the browser is IE 6.0.1 .
- the connection to the Web application is made throug https. This is way Pragma "no-cache" or similar headers could not be set otherwise the jnlp file would not get downloaded (there is an IE bug report made for that).
- in the Websphere web server all the browser requests appear as "GET" and not "HEAD".

So, the browser asks through a GET for a new jnlp file always but all it does is updating the Expiration time of the one already existing in its cache. The old one is used.

Any Ideas?

Arto Pastinen
Ranch Hand

Joined: Dec 13, 2002
Posts: 79
is it possible to use very small expiration value?
Cristian Negresco
Ranch Hand

Joined: Sep 15, 2001
Posts: 182

Yes, the problem was with the JnlpDownloadServlet. The browser sends a GET with "if-expired-since" and the servlet decides the file is not modified because it is the same on the file system. The problem is that I am using some servlet filters to modify the jnlp file and because the behavior of the servelet the jws receives the old jnlp file, with the old dynamic fields.

I agree. Here's the link:
subject: IE & JNLP
jQuery in Action, 3rd edition