Re: SecureSoap Bug? IMHO it is a J2EE Server bug.

[George I Matkovits <ma...@uswest.net>]

>

I did two versions (AutoEnableSSL and EnableSSL to allow the addition of the HTTP1.1 String for supporting keep-alives (by the former). The  EnableSSL() call does not do that and IMHO your client code should work with it. In the upcoming version I would like to force EnableSSL automatically but I can
not do it because a new URL for https can not be created without doing EnableSSL 1st. This is not really a SecureSoap but J2EE application server bug (-: I have plenty of my own). ALL Web servers should accept the HTTP 1.1 string, that is supposed to be the standard (-: Apache and the latest Tomcat
V3.2B1+ seem to behave correctly. iPlanet (Sun/Netscape alliance) and some WebLogic (BEA) servers also do not seem to support the HTTP standard correctly. (-: Has anyone tried it on Websphare (IBM), please?
Sorry - George

> "Simpson, Jeff" wrote:
>
> I think I found out why I was not able to connect to my iPlanet machine.  Tell me if I did something wrong or found a bug.
>
> I put the following line in my code:
>         SecurityUtils.AutoEnableSSL();
>
> The Url that is Created is https//mars.ezpricing.com:443/api/rpcrouter HTTP/1.1
>
> When this is sent I do not get a connection
>
> I went into the HTTPSUtil class and changed line 166 from:
>
>         ServerUrl = new URL (StdServerUrl + " HTTP/" + httpsVersion);
> to:
>
>         ServerUrl = new URL (StdServerUrl);
>
> Now everything work well.  Is this a bug in SecureSoap so that is works with Apache but not iPlanet.  Is it really a iPlanet bug and we should fix it so it works with this popular webserver?  Can I make the code do exactly what I want by choosing to enable and not AutoEnable in the SecurityUtils?
>
> Thanks
>
> Jeffrey V. Simpson
> Senior Software Engineer
> iFINANCE
> Phone: 202.833.4949
> Fax: 202.833.3819
> URL: http://www.ifinance.com