On Wed, 2013-05-01 at 09:58 -0400, R Smith wrote: > Hello, > > I have a question on proxy chaining. > > I know that httpclient supports a single hop proxy, (Source -> P1 -> > Target) out of the box by using TUNNEL_TARGET. However, when I provide an > extra proxy in the chain using a custom HttpRoutePlanner#determineRoute(), > (Source -> P0 -> P1 -> Target) I use TUNNEL_PROXY and need to implement a > custom DefaultRequestDirector#createTunnelToProxy(). Im just not sure what > all should be done in this method. My route object looks correct, I can > see both proxies and target but Im just not sure if I need to make a > connection to the 1st proxy using a custom HttpConnect method object. I > noticed there is no Http "CONNECT" method, there is HttpGet, HttpPost and > HttpDelete. Should I create my own HttpConnect object for proxy chaining > or can I accomplish the "Connect" command on the 1st proxy in the chain > some other way? > > Any example code or advice would be appreicated, thank you. > -Ryan
Ryan, HttpClient routing API is fully proxy chaining aware. However, request execution code presently only supports connection tunneling through a single proxy only. Protocol logic for proxy chaining still needs to be implemented. There is no class representing CONNECT method in HttpClient because it is a special purpose method and as such it should never be executed by the end users of HttpClient. Hope this makes some sense. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
