Thanks Oleg. I read the release notes for 4.3.5 prior to posting, and didn't see this bug listed.
Todd Lainhart Rational software IBM Corporation 550 King Street, Littleton, MA 01460-1250 1-978-899-4705 2-276-4705 (T/L) [email protected] From: Oleg Kalnichevski <[email protected]> To: HttpClient User Discussion <[email protected]> Date: 08/15/2014 12:11 PM Subject: Re: A question regarding proxy authentication On Fri, 2014-08-15 at 11:48 -0400, Todd W Lainhart wrote: > HttpClient 4.3.4 > > The scenario I'm testing is an authenticating forward proxy and an > authenticating target. The RequestConfig is built setting > authenticationEnabled to false in general, as I need to follow/handle the > authentication challenges from the target in my code. The existence of > the proxy in the environment is conditional, and whether or not it's an > authenticating proxy is also conditional. In this case the proxy exists > and is authenticating. > > Debugging into MainClientExec, createTunnelToTarget(...) is the code that > handles the route to the proxy. In that code, it appears that the > expectation is that the authenticationEnabled will need to be set in order > to handle a 407 response. In other words, if a 407 is returned from the > server, and authenticationEnabled is false, the connect request is > replayed, and httpclient gets an IO error from the server. Otherwise, the > tunnel request might endlessly loop. > > Am I mis-using the library? It looks like I can't get around setting > authenticationEnabled to true in this case. > > No, you are not. Please upgrade to 4.3.5. See HTTPCLIENT-1531 for details [1] Oleg [1] https://issues.apache.org/jira/browse/HTTPCLIENT-1531 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
