PROTECTED]
30.09.2003 17:31
Please respond to Commons HttpClient Project
To: [EMAIL PROTECTED]
cc:
Subject:RE: Prompting user for authentication?
Great! I'll look forward to that release then. (BTW, got a rough target
date for release?) In the meantime, my current
Roland Weber wrote:
Hello David,
I've taken the liberty to copy your mail as a comment to the bug:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10794
to get the discussion starting. I want to add some comments
of my own, and the discussion should be tracked with the bug.
Please use the
No problem. Thanks for doing that...
David
-Original Message-
From: Roland Weber [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 2:24 AM
To: Commons HttpClient Project
Subject: RE: Prompting user for authentication?
Hello David,
I've taken the liberty to copy your mail
Project
To: [EMAIL PROTECTED]
cc:
Subject:Prompting user for authentication?
I've been working with HttpClient for the past few days and have it just
about working to my liking. I must say I really like how it's designed!
However there's one bit that still
Hello David,
on second thought, if you want some kind of automatic handling,
you can try to substitute a different HttpMethodDirector (in 2.1).
There's probably no public API for that yet, but it's the perfect
place for such stuff.
regards,
Roland
One of our engineers developed a patch for HttpClient which allows a callback
handler to be registered with an HttpClient instance. A registered handler
could prompt the user for username/password. When a handler isn't
registered, the HttpClient works as it does now.
-Steve
On Monday 29
On 30/09/2003 10:12 PM, Steve Vaughan [EMAIL PROTECTED] wrote:
One of our engineers developed a patch for HttpClient which allows a callback
handler to be registered with an HttpClient instance. A registered handler
could prompt the user for username/password. When a handler isn't
Project
Subject: Re: Prompting user for authentication?
I disagree. It seems counter-intuitive to me that every application that uses
HttpClient should have to provide the same block of code to perform a
function as fundamental as authentication. HttpClient already handles most
authentication
HttpClient Project
Subject: Re: Prompting user for authentication?
I disagree. It seems counter-intuitive to me that every application that
uses HttpClient should have to provide the same block of code to perform a
function as fundamental as authentication. HttpClient already handles most
: Tuesday, September 30, 2003 4:23 PM
To: Commons HttpClient Project
Subject: Re: Prompting user for authentication?
Oleg,
I was aware of the bug writeup, but hadn't noticed the target milestone. I
see that the status is still NEW, so I assume that work hasn't started. I
would be happy to donate
: RE: Prompting user for authentication?
Steve,
Integrated callbacks are planned for the next release (currently designated
as 2.1)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10794
Oleg
-Original Message-
From: Steve Vaughan [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30
PROTECTED]
Sent: Tuesday, September 30, 2003 17:32
To: [EMAIL PROTECTED]
Subject: RE: Prompting user for authentication?
Great! I'll look forward to that release then. (BTW, got a rough target
date for release?) In the meantime, my current solution will work, as I
don't *have* to support NTLM
Ok...thanks!
-Original Message-
From: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 10:00 AM
To: Commons HttpClient Project
Subject: RE: Prompting user for authentication?
David,
Regarding release target dates, all I can do is to offer my guesstimates
I've been working with HttpClient for the past few days and have it just
about working to my liking. I must say I really like how it's designed!
However there's one bit that still bugs me...authentication of proxy and web
servers (response codes 401 and 407). Basically, what I'd like to do is
14 matches
Mail list logo
