Return-Path: Mailing-List: contact soap-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-user@xml.apache.org Received: (qmail 17652 invoked from network); 5 Aug 2000 02:17:29 -0000 Received: from unknown (HELO enterprise.ezpricing.com) (63.140.186.62) by locus.apache.org with SMTP; 5 Aug 2000 02:17:29 -0000 Received: by enterprise.ezpricing.com with Internet Mail Service (5.5.2650.21) id ; Thu, 3 Aug 2000 10:29:50 -0400 Message-ID: <8F578FC15B1FD411ACBD000629EE639004746A@enterprise.ezpricing.com> From: "Simpson, Jeff" To: "'soap-user@xml.apache.org'" Subject: RE: Two enhancements: HTTP 1.1 keepalive and SSL Date: Thu, 3 Aug 2000 10:29:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFFD57.48100AFA" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFFD57.48100AFA Content-Type: text/plain Has anything happened with the SSL version? I would be interested in testing it. -----Original Message----- From: George I Matkovits [mailto:matkovitsg@uswest.net] Sent: Sunday, July 30, 2000 2:51 PM To: soap-user@xml.apache.org Subject: Re: Two enhancements: HTTP 1.1 keepalive and SSL I started working 'off line' on the SSL version. I would like to work with the servlet replacement of the reouter.jsp. I do not expect any interface changes. There is just going to be a new https transport and changes in some utility modules. I hope it is going to be real transparent (the URL will have https and NOT http). Regards - George p.s. SSL socket connection does not work for me but my test environment works OK over a URL connection (on Linux with Apache, mod_ssl, openssl and Tomcat). Encryption strength will depend on the type of the respective crypto jar file (its strength is export controlled). I would also like to use certificates for authentication (the APIs are there for CGI) but I am just currently researching the respective Java APIs. Tim Miranda wrote: > Two things that would definitely help > this implementation: > > 1. Optional SSL for socket operations > 2. Conforming to HTTP/1.1 and allowing > persistent connections to be requested > by the client, so each SOAP call doesn't > require a new connection. > > Any word on either of these getting > implemented? > > ................................................................... > : Tim Miranda / Software Engineer, Pegasystems / 617.374.9600 x6335 ------_=_NextPart_001_01BFFD57.48100AFA Content-Type: text/html RE: Two enhancements: HTTP 1.1 keepalive and SSL

Has anything happened with the SSL version?  I would be interested in testing it.

-----Original Message-----
From: George I Matkovits [mailto:matkovitsg@uswest.net]
Sent: Sunday, July 30, 2000 2:51 PM
To: soap-user@xml.apache.org
Subject: Re: Two enhancements: HTTP 1.1 keepalive and SSL

I started working 'off line' on the SSL version. I would like to work
with the servlet replacement of the reouter.jsp. I do not expect any
interface changes. There is just going to be a new https transport and
changes in some utility modules. I  hope it is going to be real
transparent (the URL will have https and NOT http).
Regards - George

p.s. SSL socket connection does not work for me but  my test
environment works OK over a URL connection (on Linux with Apache,
mod_ssl, openssl and Tomcat). Encryption strength will depend on the
type of the respective crypto jar file (its strength is export
controlled). I would also like to use certificates for authentication
(the APIs are there for CGI) but I am just currently researching the
respective Java APIs.

Tim Miranda wrote:

> Two things that would definitely help
> this implementation:
>
> 1. Optional SSL for socket operations
> 2. Conforming to HTTP/1.1 and allowing
> persistent connections to be requested
> by the client, so each SOAP call doesn't
> require a new connection.
>
> Any word on either of these getting
> implemented?
>
> ...................................................................
> : Tim Miranda / Software Engineer, Pegasystems / 617.374.9600 x6335

------_=_NextPart_001_01BFFD57.48100AFA--