The following behavior was observed with Java Web Start 1.6.0_10 b25
running on JRE 1.6.0_10 b25 and Java Web Start 1.6.0_03 running on
JRE 1.6.0_03.

1. explicit commandline argument
--------------------------------
 Start from command shell:
 javaws -J-Dhttp.keepAlive=false https://<host>:8443/<path>/<file>.jnlp

 This always worked fine: the parameter change was always regarded
 (default: http.keepAlive=true).

2. property set in jnlp file, jnlp file given as http URL
---------------------------------------------------------
 The property was set in the <resources> section of the jnlp file:
[ ... ]
 <resources>
    <property name="http.keepAlive" value="false"/>
[ ... ]

 The application was started from a command shell with:

 javaws https://&lt;host&gt;:8443/&lt;path&gt;/&lt;file&gt;.jnlp

 The test showed that the parameter "http.keepAlive=false" was not regarded
 for the download phase of the application.
 However, after the application was started, the parameter was found in the
 system properties dumped into the console window:

 Dump system properties ...
----------------------------------------------------
[ ... 6 lines deleted ... ]
http.keepAlive = false
https.protocols = TLSv1,SSLv3
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = C:\jre1.6.0_10\lib\deploy.jar
java.class.version = 50.0
java.endorsed.dirs = C:\jre1.6.0_10\lib\endorsed
[ ... ]


3. property set in jnlp file, jnlp file given as file URL
---------------------------------------------------------
 The property was set in the <resources> section of the jnlp file
 (like in 2.).
 The application was started from a command shell with:

 javaws C:\<file>.jnlp

 This always worked fine: the parameter change was always regarded
 (default: http.keepAlive=true).