I had a similar situation and we DO need to use thrid-party libraries. Its
true that JWS has an implementation, but I'd rather use other tools if I
were not using JWS as my Web Server.
I have tried RSA Security's (http://www.rsa.com) BSAFE SSL-J toolkit and
that seems to work fine. They give it for free for development; you have to
pay a fee for deploying it in production environment.
Ganesh
----Original Message Follows----
From: Milt Epstein <[EMAIL PROTECTED]>
To: "A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology." <[EMAIL PROTECTED]>
Subject: Re: openConnection https URL, help!!!
Date: Mon, 17 Jan 2000 09:38:01 -0600 (CST)
MIME-Version: 1.0
Received: from [204.160.241.28] by hotmail.com (3.2) with ESMTP id
MHotMailBA4C880D002DD820F3ABCCA0F11CFC2C0; Mon Jan 17 08:02:21 2000
Received: from mail (mail.java.sun.com [204.160.241.28])by mail.java.sun.com
(8.9.3+Sun/8.9.3) with ESMTP id IAA04253for <[EMAIL PROTECTED]>; Mon,
17 Jan 2000 08:01:23 -0800 (PST)
Received: from JAVA.SUN.COM by JAVA.SUN.COM (LISTSERV-TCP/IP release 1.8d)
with spool id 4253990 for [EMAIL PROTECTED]; Mon, 17
Jan 2000 07:38:45 -0800
Received: from staff1.cso.uiuc.edu (staff1.cso.uiuc.edu [128.174.5.59]) by
mail.java.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA28870 for
<[EMAIL PROTECTED]>; Mon, 17 Jan 2000 07:38:44 -0800 (PST)
Received: from localhost by staff1.cso.uiuc.edu (8.9.3/8.9.3) with ESMTP id
JAA12311 for <[EMAIL PROTECTED]>; Mon, 17 Jan 2000
09:38:01 -0600 (CST)
>From [EMAIL PROTECTED] Mon Jan 17 08:06:01 2000
X-Authentication-Warning: staff1.cso.uiuc.edu: mepstein owned process doing
-bs
X-Sender: [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
On Mon, 17 Jan 2000, Yang XIAO wrote:
> Hi, there
>
> I wrote an servlet that can connect a http URL, but in reality I want to
> openConnection with a https URL. With the same code, I got err when I
tried
> https one:
>
> java.net.MalformedURLException: unknown protocol: https
> at java.net.URL.<init>(URL.java)
> at java.net.URL.<init>(URL.java)
> at TalkPegasus.main(TalkPegasus.java:7)
>
> Anyone's suggestion will be highly appreciated!!
For your servlet to act as an SSL client (which is essentially what
you're doing when you open an https URL), you need some extra classes
to handle that. This has been discussed on the list somewhat, you
might check the archives. I believe there were some third party
classes that would do the trick, and there might actually be some from
Sun (and I believe the JWS supported it internally, but that may not
be feasible for you, and I don't know what's the latest on that).
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
