RE: SSL Soap

["Nelson, Christopher" <cn...@synchrony.net>]

Sorry for the lateness of my reply, but I did not read the last couple
sentences initially ;)  For my code I added a couple lines to RPCRouter
servlet to access the header and send it to the target object.  But with the
new provider code, it would be easier to just go ahead write a user defined
provider that got the headers, did whatever to them, and then delegated to a
java provider.  To add the headers on the client side I just used
call.setHeader() I think.  Can you go ahead and check in your SSL code?  I'm
using SSL stuff, but also want to use the latest code changes with
EnvelopeEditor and Provider so I would very much like to see SSL merged in.
If you want, I can look into doing the merge myself if you are busy.  Let me
know.

Thanks,

-----Original Message-----
From: George I Matkovits [mailto:matkovitsg@uswest.net]
Sent: Monday, October 30, 2000 10:14 PM
To: soap-dev@xml.apache.org; cnelson@synchrony.net
Subject: Re: SSL Soap


Thank you for the testing effort. I have the HTTP/1.1 string appended
because
IMHO it is part of the HTTP spec. The current generation of J2EE App.
Servers
and 'older' Tomcat Versions seem to choke on this. In the next version I
will
have a global flag in Soap.properties to override the generation of this
string.
I would like to have  it left in for the future because the Next Gen.
Servers
might only do HTTP1.1 provided 'keep-alive' support when explicitly
requested.
This is one of those 'small letter' parts of the HTTP spec. I would also
like a
small favor to ask. I need to put some headers also into Soap but I do not
know
where to break into the code for header support. You  must have already
solved
the problem for your SSL password  effort. My problem is not the generation
of
header elements but where to break into the code with as little disturbance,
and
rewrite as possible. (-:  like I done it for SSL.
Regards - George

"Nelson, Christopher" wrote:

> I have been testing SSL SOAP with weblogic 4.5.1 and ran into a small
> problem.  Weblogic did not like having the HTTP/1.1 at the end of the URL.
> In HTTPSUtils, at the line where the URL is built I removed this.  After
> that it worked fine.  Oddly enough, this behavior occurred only at a
certain
> weblogic service patch level (4.5.1sp11).  Just thought I'd share my
> experience