Hi Mike & Mike Michael Becke wrote:
> Given that HttpClient is in the business of communicating using HTTP, > it is not terribly well suited for other purposes. Since CONNECT is also an HTTP method, it is not totally out of scope for the HttpClient. From RFC 2616, section 9.9: > This specification reserves the method name CONNECT > for use with a proxy that can dynamically switch to being > a tunnel (e.g. SSL tunneling [44]). Maybe we can consider official support for CONNECT as a feature for the big 4.0 API overhaul. cheers, Roland
