That's what I thought when I first looked at it but it appears to use
the JDK connection classes.
A grinder transcript using HttpUnit (succeeds) and HttpClient (fails)
follows. One thing that's odd is that the HttpClient transaction looks
more like the transcript I get with IE than does the one
Hi Brett,
This is a bit of a guess, but it could be because of the cookie format.
Try using the cookie compatibility setting:
CookiePolicy.setDefaultPolicy(CookiePolicy.COMPATIBILITY);
Mike
On Feb 2, 2004, at 3:57 PM, Brett Knights wrote:
That's what I thought when I first looked at it
FWIW when I replaced HttpClient with the WebClient classes from
HttpUnit it all works again.
- Original Message -
From: Brett Knights [EMAIL PROTECTED]
To: Commons HttpClient Project
[EMAIL PROTECTED]
Sent: Tuesday, January 27, 2004 3:39 PM
Subject: Re: Odd problem
Thanks
,
Roland
Brett Knights [EMAIL PROTECTED]
27.01.2004 06:15
Please respond to Commons HttpClient Project
To: Commons HttpClient Project
[EMAIL PROTECTED]
cc:
Subject:Odd problem
Hi,
I am using RC3 with jdk 1.4.2_03
When I use http client to get to the site
.
- Original Message -
From: Roland Weber [EMAIL PROTECTED]
To: Commons HttpClient Project
[EMAIL PROTECTED]
Sent: Monday, January 26, 2004 10:24 PM
Subject: Re: Odd problem
Hello Brett,
the 11b should be part of the chunked encoding used by
the server to send back the error page. No reason
Hi,
I am using RC3 with jdk 1.4.2_03
When I use http client to get to the site I get a 404 (http client
wire log follows then grinder generated IE trace). I just can't see
what is going wrong. Any suggestions are appreciated. This is part of
a larger scripted operation so I am wondering if if
