DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28151>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28151 Proxy tunneling/auth with CONNECT for non-HTTP protocols ------- Additional Comments From [EMAIL PROTECTED] 2004-04-05 05:04 ------- Oleg, I agree, the ProxyClient is a much better way to handle this. I have made just a few changes to your patch to simplify things a little. In particular ProxyClient now makes use of the HttpMethodDirector instead of handling authentication on its own. Mike, in regard to your question, you are correct. You will be able to have full control over how the socket is created. The only caveat is that if you want to tunnel SSL you will need to force the proxy to connect to port 443. For example: proxyclient.getHostConfiguration().setHost("SSL-host", 443); If a port is not specified, the protocol default (usually 80) will be used. I imagine these changes will be part of the 3.0 release. Pinning down an exact ETA for 3.0 may be a little difficult. Does anyone have a particular schedule in mind? Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
