Its looks like the first GET is challenged and the credentials are provided
but when executing the second GET the authentication is requested for a
different realm but because the AuthState already had credentials they were
used.
The member targetAuthState in DefaultRequestDirector holds the old
On Tue, 2014-03-25 at 09:29 +0200, d_k wrote:
Its looks like the first GET is challenged and the credentials are provided
but when executing the second GET the authentication is requested for a
different realm but because the AuthState already had credentials they were
used.
The member
Thank you very much for the support. :-)
So it appears that upgrading httpclient won't solve this issue?
On Tue, Mar 25, 2014 at 11:27 AM, Oleg Kalnichevski ol...@apache.orgwrote:
On Tue, 2014-03-25 at 09:29 +0200, d_k wrote:
Its looks like the first GET is challenged and the credentials
Alright. Thank you very much for the help!
Currently JIRA (https://issues.apache.org/jira/browse/HTTPCLIENT) is down
for maintenance but i'll open an issue when its back online.
On Tue, Mar 25, 2014 at 12:02 PM, Oleg Kalnichevski ol...@apache.orgwrote:
On March 25, 2014 10:55:20 AM CET, d_k
Hello.
I'm using httpclient-4.1.1 and i'm trying to authenticate with different
users on different realms but it seems to fail.
i create several AuthScope objects with the same host and port and a
different realm for each one.
If I pass schema as null then httpclient will attempt to send the
On Mon, 2014-03-24 at 17:54 +0200, d_k wrote:
Hello.
I'm using httpclient-4.1.1 and i'm trying to authenticate with different
users on different realms but it seems to fail.
Before I even start looking into this, is there a reason you are not
using a newer version of HttpClient (preferably
On Mon, 2014-03-24 at 18:38 +0200, d_k wrote:
I'm upgrading a Nutch plugin that used httpclient 3.x and because Nutch was
already dependent on httpclient 4.1.1 I decided to avoid adding a new
dependency on httpclient 4.3 and use the existing dependency on 4.1.1
I can take a look at the
