It may work, depending on your Web server configuration, the issue being as follows. To use an SSH tunnel, you would point your SOAP client at the local tunnel endpoint, which would be localhost:someport. That tells the SOAP client where to connect the socket, which works create. However, the SOAP client will also use that address to create the HTTP Host header. The actual host:port of the Web server will be something different. If the Web server ignores the header, everything will work fine. However, in many configurations, the Host header is used by the Web server to determine the virtual host to which to route the request. In such a configuration, the header will not map to a virtual host, and the request will be rejected.
This is true of all tunnels (also known as relays or circuit-level relays). For example, TcpTunnelGui that comes with Apache SOAP, or Simon Fell's excellent tcpTrace (http://www.pocketsoap.com/). That is why proxies, such as Simon's proxyTrace, are preferable for intercepting messages for debugging. Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: "Bassem HAIDAR" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 09, 2003 5:08 AM Subject: Re: SOAP over SSL with IBM JSSE > Hello > > Does SAOP over SSH exist ??? > > > > > >
