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
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
/nllogin.nl[\r][\n]
IE:
Referer:
https://target.com/pages/login.jsp?rdt=%2Fapp%2Fcenter%2Fmyroles.nl
You could try to set a different Referer header in your request.
best regards,
Roland
Brett Knights [EMAIL PROTECTED]
27.01.2004 06:15
Please respond to Commons HttpClient Project
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
Would the intention of this be to reproduce the functionality of
java.net.URI
as found in J2SE 1.4?
java.net.URI seems quite complete.
If so how many people can't make the switch to 1.4? I am not using
1.4.x in producion yet but I have been doing all my development with
1.4.1 so at this point it
