ssage-
From: Daniel Rall [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 26, 2002 8:04 AM
To: [EMAIL PROTECTED]
Subject: Re: Netscape browser/applet problem with SSL
"Rick Johnston" <[EMAIL PROTECTED]> writes:
> Very interesting. This would say to me that XMLRPC canno
Daniel Rall wrote:
>
> "Rick Johnston" <[EMAIL PROTECTED]> writes:
>
> > Very interesting. This would say to me that XMLRPC cannot be used in an
> > applet running in a Netscape browser with an SSL connection, since the
> > browser usually doesn't supply valid content-length header information
"Rick Johnston" <[EMAIL PROTECTED]> writes:
> This is going off on a slight tangent, but the reason for the applet to use
> the browser for the SSL connection is that otherwise the applet has to
> download JSSE to have the HttpsURLConnection class. By using
> URL.openConnection(), the applet doe
|
| cc:
|
| Subject: Re: Netscape browser/applet problem with SSL
|
>---|
"Rick Johnston"
"Rick Johnston" <[EMAIL PROTECTED]> writes:
> Very interesting. This would say to me that XMLRPC cannot be used in an
> applet running in a Netscape browser with an SSL connection, since the
> browser usually doesn't supply valid content-length header information
> (even when the java code attem
|
| Subject: Re: Netscape browser/applet problem with SSL
|
>--|
"Rick Johnston" <[EMAIL
"Rick Johnston" <[EMAIL PROTECTED]> writes:
> I've just had to deal with a problem peculiar to Netscape browsers running
> an applet using XMLRPC. It is apparently a known problem that applets
> (we're using JRE 1.3.1 via the plug-in) on most versions of Netscape
> browsers don't send reliable H
I've just had to deal with a problem peculiar to Netscape browsers running
an applet using XMLRPC. It is apparently a known problem that applets
(we're using JRE 1.3.1 via the plug-in) on most versions of Netscape
browsers don't send reliable HTTP header information when using an SSL
connection
