> Because I'm using JSSE, I'm looking at the patch at the URL above that was > associated with JSSE to see how to make Apache SOAP clients work using HTTPS > with a proxy server. Does anybody understand how proxying over HTTPS "ought > to work"? That is, is the client supposed to open a connection the proxy > server over HTTP first, give it some info, and then send the SSL-encrypted > data? Is Apache SOAP supposed to handle this already?
https and proxies works as follows: the client creates a connection to the proxy (as usual), and then sends a CONNECT request, giving the host and port of the server the client is trying to talk to. If ok, the proxy creates a connection to the desired server and then sends back a 200 response to the client, and from then on acts like a tunnel, i.e. just blindly shuffles packgets between the two. At that point the client basically has a connection with the server, so it starts the usual SSL handshake and sets up the secure connection. As far as seeing that in the code: you'll see the method enableSSLTunneling in HTTPClient which sets up the tunnel through the proxy. After that an SSL-socket is wrapped around the underlying socket. Does anybody know if SOAP 2.2 was designed to work this way? Thanks, David
