Thanks for the help. Wireshark it is then ;-) -----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Monday, 18 August 2008 9:38 p.m. To: JMeter Users List Subject: Re: JMeter Unable to parse header
On 18/08/2008, Oliver Erlewein (DSLWN) <[EMAIL PROTECTED]> wrote: > Sa I read the bug this is just an output error in the log. That means that > the real error/problem is probably something different? > Yes. > Would that fix be in a nightly build? I don't think there are any for HttpClient 3.x Looks like you'll need to use Wireshark or something similar, sorry. > Cheers Oliver > > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: Monday, 18 August 2008 11:34 a.m. > To: JMeter Users List > > Subject: Re: JMeter Unable to parse header > > On 18/08/2008, Oliver Erlewein (DSLWN) <[EMAIL PROTECTED]> wrote: > > Hi sebb, > > > > Here's what causes the error: > > httpclient.wire.header: << "HTTP/1.1 200 OK[\r][\n]" > > 2008/08/15 16:47:51 DEBUG - httpclient.wire.header: << "Date: Fri, 15 Aug > 2008 04:47:51 GMT[\r][\n]" > > 2008/08/15 16:47:51 DEBUG - httpclient.wire.header: << "Server: > Microsoft-IIS/6.0[\r][\n]" > > 2008/08/15 16:47:51 DEBUG - httpclient.wire.header: << "X-Powered-By: > ASP.NET[\r][\n]" > > 2008/08/15 16:47:51 DEBUG - httpclient.wire.header: << "Set-Cookie: > EducationSSO=AQIC5wM2LY4SfcwChz3FBPfPFpIpmsGoKtr%2BhlqSEuEWaks%3D%40AAJTSwAKLTg4NjUxMjIyNgACU0kAAjEwAAJTMQACMDE%3D%23;Path=/[\r][\n]" > > 2008/08/15 16:47:51 DEBUG - httpclient.wire.header: << "HTTP/1.1 200 > OK[\r][\n]" > > > > The issue is the second 200 OK. That should not be there. The developers > are having a look into it. When I do the same thing in FireFox with Live HTTP > headers or Tamper Data tracing the responses this line does not appear and > the response is complete. I don't know if a browser would ignore that line > and continue processing. > > That could be due to the following bug: > > https://issues.apache.org/jira/browse/HTTPCLIENT-743 > > AFAIK, the fix is not in the current release. > > > > Regards & Thanks! > > Oliver > > > > -----Original Message----- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: Saturday, 16 August 2008 12:11 a.m. > > To: JMeter Users List > > Subject: Re: Jmeter Unable to parse header > > > > On 15/08/2008, sebb <[EMAIL PROTECTED]> wrote: > > > On 15/08/2008, Oliver Erlewein (DSLWN) <[EMAIL PROTECTED]> wrote: > > > > Hello all, > > > > > > > > I'm getting an error going to a website that runs fine on Firefox > and IE. I've checked that all Cookies & Co are set like they are when the > browser uses them. The error is: > > > > > > > > org.apache.commons.httpclient.ProtocolException: Unable to parse > header: HTTP/1.1 200 OK at > org.apache.commons.httpclient.HttpParser.parseHeaders(HttpParser.java:202) > > > > > > > > > <snip/> > > > > > > > > > > I've seen a similar thing here: > > > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg01288.html > > > > > > > > Since I don't see what JMeter's getting back I can't help with > more. Hope someone can help me here. > > > > > > > > > Looks like HttpClient is confused by the server response. > > > > > > Normally I'd suggest to switch on HttpClient wire header logging: > > > > > > log_level.httpclient.wire.header=debug > > > > > > But the quoted message shows that probably won't help. > > > > > > > I should have read the JIRA issue fully - the problem was fixed for > > HttpClient 3.1, which is included in the current JMeter version. > > > > So please can you try that? > > > > > You could use something like Wireshark to examine the server response. > > > > > > Also you could try using the default HTTP sampler for this sample. > > > > > > > > > > > Cheers > > > > > > > > Oliver > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
