I've narrowed down a file caching problem we have, where clients that modify files on the server are unable to see these changes within the webstart application. One server doesn't see the issue. I have the file http://www-pw.physics.uiowa.edu/~jbf/autoplot/changing/temp.htm which is updated once every minute (with a cron job) and our software that plots this data can see the changes. The other server, which is updated via svn, doesn't propagate updates when I update the file. See http://emfisis.physics.uiowa.edu/pub/jy/dev/jbf/20150515_bug1393/temp.htm.
Here are the response headers on the working server, before and after a change:
HTTP/1.1 200 OK
Date: Fri, 15 May 2015 19:51:35 GMT
Server: Apache/2.0.63
Last-Modified: Fri, 15 May 2015 19:51:03 GMT
ETag: "51dc74f-211-2a0297c0"
Accept-Ranges: bytes
Content-Length: 529
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html
-----
HTTP/1.1 200 OK
Date: Fri, 15 May 2015 20:01:00 GMT
Server: Apache/2.0.63
Last-Modified: Fri, 15 May 2015 20:00:03 GMT
ETag: "51dc74f-20f-4a3256c0"
Accept-Ranges: bytes
Content-Length: 527
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html
And on the non-working server that doesn't work, before and after the change
HTTP/1.1 200 OK
Date: Fri, 15 May 2015 20:07:20 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Fri, 15 May 2015 20:07:02 GMT
ETag: "217-51624632eaaa3"
Accept-Ranges: bytes
Content-Length: 535
Vary: Accept-Encoding
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
-----
HTTP/1.1 200 OK
Date: Fri, 15 May 2015 20:09:18 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Fri, 15 May 2015 20:09:02 GMT
ETag: "210-516246a5fc440"
Accept-Ranges: bytes
Content-Length: 528
Vary: Accept-Encoding
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Does anyone know why webstart would work fine with one server but not the other? Is there anything I can do to disable caching in webstart, that would still allow the .jar files to be cached? I've tried experimenting with this on a single-jar release that doesn't use webstart, and it seems to work fine from both websites.
Thanks,
Jeremy