Hi, again.
In case you are interested, here is the link to the Java Web Start discussion forum:
http://forum.java.sun.com/forum.jspa?forumID=38&start=0
I took a quick look there and found this entry
http://forum.java.sun.com/thread.jspa?threadID=5180200&tstart=0 which seems to describe your situation very closely. Clicking through to the bug mentioned there (here's the link to the bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6514485) it sounds as if there may be an issue in Java Web Start.
Briefly, it looks as if in Java SE 6 the Java Web Start client checks its cache and if the requested file is there the client sends a GET request to the server with the "if-modified-since" HTTP request header variable set. Previously (Java SE 5 and before) the Java Web Start client would send a HEAD request to get the timestamp of the file on the server and compare that value with the timestamp on the cached copy, then send a GET request if the cache was obsolete.
When the GlassFish Java Web Start servlet receives a request for a JAR file, it delegates the request to the default servlet provided by the web container. I am checking with my friends who work on the web container to make sure that it handles the "if-modified-since" header variable.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=221108