JDK-4393950 : request to allow codebase to be specified with an HTTPS location.
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: jaws-1.0,1.0.1
  • Priority: P5
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_98,windows_2000
  • CPU: generic,x86
  • Submitted: 2000-11-30
  • Updated: 2002-08-09
  • Resolved: 2002-02-15
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 Availabitlity Release.

To download the current JDK release, click here.
1.2.0 1.2Fixed
Related Reports
Duplicate :  
> > > Mike wrote: 
> > > Do you currently support, or plan to support, secure (HTTPS) data refs?
> > > I tried codebase="https://..." and JWS complained that the codebase was
> > > invalid.
> >
> > Rene wrote:
> > You can use the JSSE (Java Secure Socket Extension) optional package with
> > your application to get support for HTTPS.
> Mike wrote:
> My application already supports HTTPS. I am referring to your JNLP spec.
> Specifically, the "codebase" section does not support HTTPS locations.
> Again, future enhancement.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.2 hopper FIXED IN: 1.2 hopper INTEGRATED IN: 1.2 hopper VERIFIED IN: 1.2 hopper-rc

WORK AROUND Use JMF instead.

SUGGESTED FIX Get Apple to install their QTJava extention in the extentions directory.

EVALUATION See the comment section. This is currently not deemed to be a critical feature. This also puts more demand on the JNLP Client implementor. However, JRE 1.4 is suppose to require HTTPS as part of core. So the JNLP specification could require this when a JNLP Client is used by a 1.4 or above JRE. rene.schmidt@eng 2001-01-15