If you want to use the 2.0 code, you'll need to subclass HttpState and override
getProxyCredentials() to prompt for the Credentials object. Then, when you create
your HttpClient object, you'll need to set it's HttpState to this new subclass.
David
-Original Message-
From: Russell,
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
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 authentication just yet. I would suspect that
any authorization callback handler would need to pass along the host, port,
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
