You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Davanum Srinivas <da...@gmail.com> on 2006/09/18 00:56:59 UTC
Re: WS-Security and HTTPS compatibility
Please switch on http client logging and create a JIRA issue with the results.
http://jakarta.apache.org/commons/httpclient/logging.html
thanks,
dims
On 9/17/06, Dale Herrig <Da...@copart.com> wrote:
>
>
> BTW, this is the stack trace we are getting,
>
> org.apache.axis2.AxisFault: Unconnected sockets not implemented; nested
> exception is:
> java.net.SocketException: Unconnected sockets not implemented;
> nested exception is:
> org.apache.axis2.AxisFault: Unconnected sockets not implemented;
> nested exception is:
> java.net.SocketException: Unconnected sockets not implemented
>
>
> -----Original Message-----
> From: Dale Herrig
> Sent: Sunday, September 17, 2006 9:06 AM
> To: Axis-User@Ws. Apache. Org (E-mail)
> Subject: WS-Security and HTTPS compatibility
>
>
>
> Hi,
>
> We implemented WS-Security meaning we digital sign and digital encrypted
> the SOAP body. This works very well and as expected. The next step was to
> have our Server and our Clients run over HTTPS (SSL). At this point we ran
> into lots and lots of problems. Are WS-Security and HTTPS compatible with
> each other. If so, are their any special requirements that the server and
> client must follow, could you point me to any document that might be useful
> in this area.
>
> Thanks,
>
> Dale
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org