United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6526242 JDK 6: Java Web Start should not set no-cache header when making http connections
JDK-6526242 : JDK 6: Java Web Start should not set no-cache header when making http connections

Details
Type:
Bug
Submit Date:
2007-02-17
Status:
Open
Updated Date:
2014-05-20
Project Name:
JDK
Resolved Date:
Component:
deploy
OS:
generic
Sub-Component:
webstart
CPU:
generic
Priority:
P3
Resolution:
Unresolved
Affected Versions:
6
Targeted Versions:
8-pool

Related Reports
Relates:

Sub Tasks

Description
I just tried out the webstart version of jext at http://www.jext.org/ with 6.0:

The first time I started the app webstart started downloading the required files. Midway through it stalled. The estimated completion time increased second for second. And from time to time webstart displayed that the download had stalled. I waited for about half a minute. Webstart made no attempt to restart the download or otherwise handle the situation.

This is a good example of lack of what I like to call "defensive coding". In the consumer space our code needs to be resilient enough to handle problems that may come out way. Do you have an idea of what might have caused this?

                                    

Comments
EVALUATION

It seems like it's much easier to run into the stall with Java 6.   In Java 6, we set the http request headers:

Cache-Control: no-cache                       Pragma: no-cache

by calling URLConnection.setUseCaches(false).

If I take away "Cache-Control: no-cache", I cannot reproduce the stall.

In Java 5, we only set "Pragma: no-cache".

For Java Web Start, I don't see why we need these no-cache headers at all actually.
                                     
2007-02-17



Hardware and Software, Engineered to Work Together