JDK-6433293 : jaws: using 1.4.2 or 5.0 over https on Solaris: Java 1.4+ is required for HTTPS support
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.4.2_12
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris
  • CPU: generic
  • Submitted: 2006-06-02
  • Updated: 2010-07-29
  • Resolved: 2006-06-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
1.4.2_13Fixed 6 b90Fixed
Description
By using a Java Webstart Application (testcase attached) with latest JRE 1.4.2 or JRE 5.0 over https on Solaris (sparc or x86), a dialog is shown with a unsuitable error message called 

   An error occurred while launching/running the application
   Category: Launch File Error

   The field <jnlp> has an invalid value: https
   Java 1.4+ is required for HTTPS support

The error dialog appears if the testcase runs on
- Solaris with JRE 1.4.2 or 5 over https

The error dialog doesn't appear if the testcase runs on
- Solaris with JRE 1.4.2 or 5 over http
- Solaris with JRE 6 over https
- Windows with JRE 1.4.2, 5 over https

How to reproduce the problem
1. Set up a webserver which can accept https connection, and which is aware of jnlp
2. Extract the testcase to the document root.
3. Modify the codebase in the .jnlp files
4. Use JRE 1.4.2_12 or JRE 5u7
5. Use a browser on Solaris (Mozilla or Firefox) and go to the testcase folder. 
6. You will see the error message which is mentioned above

A setup on SWAN exisits. See comments.
Comments
EVALUATION also removing mustang-na keywork because the wrong error message can be caused in mustang as well.
09-06-2006
EVALUATION Although the specific testcase dosn't fail the same way on mustang, the underlying problem in LaunchDescFactory, which prints out the wrong error message, should be addressed. Ill open a sub-cr for the escallated work being done in tiger.
09-06-2006