Hi Oleg, > The trouble is that any sort meaningful tunneling component most likely > would require at least rudimentary HTTP authentication support (http- > auth) and ability to retry HTTP requests (HttpMethodExecutor). Without > these features ProxyConnectMethod and HttpProxyHost would be of very > marginal use only.
That's why we are working on a componentized architecture, right? If people need authentication in addition to the simple stuff, they add http-auth to their dependencies. Should we move the AuthChallengeHandler and StdAuthChallengeHandler to http-auth? HttpMethodExecutor is available in http-common anyway. I feel comfortable with Michael's proposal of moving the proxy stuff to http-common rather than introducing a separate component. Since we don't intend to provide explicit tunneling support except for HTTP and HTTPS, a component may be overblown. cheers, Roland
