Hi Sid,
HttpClient only supports using Basic authentication preemptively. This
is because both NTLM, and Digest require values sent by the server as
part of the Authorization request to create the authorization response.
Mike
On Jan 2, 2004, at 4:15 PM, Sid Subr wrote:
on the same note of pr
figured to log 'httpclient.wire' and 'org.apache.commons.httpclient'
> category of events at DEBUG verbosity. Please refer to commons-logging &
> Log4J documentation for details
>
> Oleg
>
> -Original Message-
> From: Zulfi Umrani [mailto:[EMAIL PROTEC
ed to log 'httpclient.wire' and 'org.apache.commons.httpclient'
category of events at DEBUG verbosity. Please refer to commons-logging &
Log4J documentation for details
Oleg
-Original Message-
From: Zulfi Umrani [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 17:03
To: Kalnich
logging & Log4J documentation for details
Oleg
-Original Message-
From: Zulfi Umrani [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 17:03
To: Kalnichevski, Oleg; [EMAIL PROTECTED]
Subject: RE: preemptive
What do you mean by "eliminating the authentication ove
is going you might want to use Log4j toolkit that allows greater control
over logging (for instance, you can specify a separate log file for a
specific category of events). We will not be able to help you unless we
can see the logs.
Oleg
-Original Message-----
From: Zulfi Umrani [mailto:[EMAIL
able to figure out what
is going you might want to use Log4j toolkit that allows greater control
over logging (for instance, you can specify a separate log file for a
specific category of events). We will not be able to help you unless we
can see the logs.
Oleg
-Original Message-
From
specific category of events). We will not be able to help you
unless we can see the logs.
Oleg
-Original Message-
From: Zulfi Umrani [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 16:27
To: [EMAIL PROTECTED]
Subject: RE: preemptive
By setting realm as null, the pre-emptive
By setting realm as null, the pre-emptive authentication worked! But, it
sends a Basic Authorization header even if the URL is protected by
Digest! For Digest it is still making 2 trips in order to authenticate.
Which is fine for the first request, but it repeats the same thing for
the second reque
Hi Mike,
I set the properties as specified by the link you sent. It did not
produce any log on the stdout! If you have a piece of the code that does
that, please send that to me.
Thanks.
>>> [EMAIL PROTECTED] 6/9/2003 10:48:36 PM >>>
Zulfi,
Please send a wire and trace log. It is difficult to r
Zulfi,
Try setting both realm & host to null. That should do the trick
HttpClient hc = new HttpClient();
HttpState state = hc.getState();
state.setAuthenticationPreemptive(true);
// Set default credentials (realm & host are null)
state.setCredentials(null, nu
Zulfi,
*Please* at a minimum take a look at
http://jakarta.apache.org/commons/httpclient/logging.html and include a
debug log with any issue, it makes things so much easier at our end
because it saves us guessing.
You'll probably also want to take a look at
http://jakarta.apache.org/commons/ht
Zulfi,
Please send a wire and trace log. It is difficult to resolve these
sort of problems without them. Take a look at
http://jakarta.apache.org/commons/httpclient/logging.html for details.
Mike
On Monday, June 9, 2003, at 06:44 PM, Zulfi Umrani wrote:
Tried to use the Preemptive Authentic
12 matches
Mail list logo
