On Thu, 2008-01-10 at 16:06 -0500, Michael Prichard wrote:
Okfigured this one out. Add this:
// Sets whether authentication should be attempted preemptively.
client.getParams().setAuthenticationPreemptive( true );
And it seems to work perfectly. No idea
Ok, so this is the header I get from the server when initializing:
2008/01/11 09:38:14:292 EST [DEBUG] header - User-Agent: Jakarta
Commons-HttpClient/3.0.1[\r][\n]
2008/01/11 09:38:14:292 EST [DEBUG] header - Host:
mail.exchange.com[\r][\n]
2008/01/11 09:38:14:292 EST [DEBUG] header -
Ooops...I did not fully read the first message. Sorry.
The interesting thing is that when using the browser to hit that
server it does not give me a form based login screen like other
exchange servers. It pops up a window..very much like you see when
you set up a .htaccess with BASIC
What does this mean? Does it mean the username and password are
being sent on an open wire?
On Jan 11, 2008, at 9:12 AM, Oleg Kalnichevski wrote:
On Fri, 2008-01-11 at 09:06 -0500, Michael Prichard wrote:
Yes, I got this to work by adding this:
// Sets whether
Thanks Ronald,
After much reading and looking through the dev mailing list it seems
that pipelining is what I was looking for. Though saying that, it
does not seem to be very well supported in general. MozillaZine seems
to think that pipelining is not very well supported by some servers (I
On Fri, 2008-01-11 at 09:36 -0500, Michael Prichard wrote:
Ooops...I did not fully read the first message. Sorry.
The interesting thing is that when using the browser to hit that
server it does not give me a form based login screen like other
exchange servers. It pops up a
Hello Oleg!
This helped a lot! Thanks so much. I do have a question on how
HTTPClient handles cookies. If you look at this Debug info:
2008/01/11 13:31:18:443 EST [DEBUG] header - Set-Cookie:
sessionid=bf1658c3-fdc9-4f4a-aea7-abc2045dbae4; path=/[\r][\n]
2008/01/11 13:31:18:443 EST
