I ran some more experiments to narrow down the problem:
- I made a tiny test webstart project with a self signed JAR and that works
fine with 1.7u21.
- If I start the program from saved files - JNLP file on the local disk,
JAR on the disk and the JNLP adapted so it uses the local JAR -
Just looked at the headers the app sends:
HTTP/1.1 200 OK
X-TraceUrl: /appstats/details?time=1369478620521type=json
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
content-disposition: attachment;
It works if you use Java 1.7.0_17 (and Java 6). Is there a difference in
the headers with the older version?
Gary
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an
On Saturday, 25 May 2013 13:54:20 UTC+2, Gary Frederick wrote:
It works if you use Java 1.7.0_17 (and Java 6). Is there a difference in
the headers with the older version?
Gary
I don't think the headers changed, I think that javaws interprets the HTTP
headers in a stricter way. I narrowed
!!!
Thanks for the post and the research
Gary
On Saturday, May 25, 2013 7:43:39 AM UTC-5, Mathias Kegelmann wrote:
On Saturday, 25 May 2013 13:54:20 UTC+2, Gary Frederick wrote:
It works if you use Java 1.7.0_17 (and Java 6). Is there a difference in
the headers with the older version?
I'm not sure this helps, but here's what I observed:
- Looking at the stacktrace and
com.sun.javaws.security.JNLPSignedResourcesHelper,
com.sun.deploy.cache.ResourceProviderImpl.getCachedResourceFilePath
and com.sun.deploy.cache.Cache.getCachedResourceFilePath I think that
javaws is looking
