Hi Oleg, > Oleg Kalnichevski updated HTTPCLIENT-649: > --- > Roland, We do not necessarily have to provide this feature in the stock > version of HttpClient if this will increase the complexity of connection > management code dramatically. As long as the users are able to plug in > their own custom connection operator this should be sufficient.
That's the problem. I made HttpRoute a class rather than an interface, and it's not a class meant to be extended. Connection managers rely on HttpRoute to determine re-usability. CONNECT requests are generated by the director, operators are not supposed to handle it under the covers. Especially not if proxy authentication comes into play. The route building logic used by the (default) director is also tied to the limitations of HttpRoute. This will need some pondering. The quickest hack might be "ProxyChain extends HttpHost" for specifying proxies and a custom director to interpret that. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
