On Sun, 2007-08-12 at 06:30 -0700, Roei Erez wrote: > Thanks for the quick response. > I would like to get involved in implementing this feature. > I have read the 'ConnectionManagementDesign' in the wiki, and want to > come up with a good and clean design for this issue(assuming no one has > done it already). > Is this accepted?
Sure. You are very welcome to jump in. > Is there anyone that is dealing with this issue that I should talk to? Roland Weber has been doing most of the work on the connection management front lately. So, you should definitely synchronize your activities with him. He might be off-line until Friday next week, though. Meanwhile I'll be happy to help you get up to the speed with the 4.0 codebase. Please do note, though, HttpClient 4.0 is still in the very early stage of development. It is unlikely to be suitable for use in production for many more months to come. Another important thing I should mention: NTLM auth scheme has not yet been ported to the new API. In general NTLM is a very thorny and controversial subject. We are still trying to come up with a reasonable strategy of supporting NTLM authentication in future versions of HttpClient. You may want to take a look at this resource for details [1] Cheers Oleg [1] http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions > Thanks in advance, > Roei Erez. > > -----Original Message----- > From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 12, 2007 2:07 PM > To: HttpComponents Project > Subject: Re: Apache httpclient with NTLM > > On Sun, 2007-08-12 at 04:27 -0700, Roei Erez wrote: > > Hi all, > > > > I am developing a server-side application, where different users (each > > one has his own credentials) make http requests against a remote > server. > > > > I am using Apache HTTPClient in the server side (let's call it 'A') to > > make the actual HTTP Requests against another remote server (let's > call > > it B). > > > > The authentication method of server 'B' is NTLM. > > > > My problem is that NTLM authenticate a connection, and therefore, > after > > one user makes an HTTP request using one connection, the connection is > > authenticated with his credentials and the next user that gets this > > pooled connection will use an authenticated connection that is > populated > > with the first user credentials. > > > > > > > > I think that the way to solve this problem should be by having the > > HttpConnectionManager, on some cases, maintain pools by host and user > > credentials, and not only by host. > > > > One of the problems is that this requires changes to the API of > > HttpConnectionManager. > > > > Does any one have an idea of how to handle this annoying issue? > > > > Hi Roei > > We are aware of the problem [1] and will provide a proper solution to it > in HttpClient 4.0. As far as HttpClient 3.1 the only feasible workaround > (besides developing a custom connection manager from scratch) is to > maintain a separate connection manager instance on a per user basis. > > Oleg > > [1] https://issues.apache.org/jira/browse/HTTPCLIENT-652 > > > Regards, > > > > Roei Erez. > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
