[Webtest] Diagnosis of reported URL Errors

[Edgar P Dollin]

Thanks...I'll give it a try.

Edgar

> -----Original Message-----
> From: Luca Scheuring [mailto:lscheuring@dplanet.ch]
> Sent: Friday, October 01, 2004 3:15 AM
> To: webtest@gate2.canoo.com
> Subject: AW: [Webtest] Diagnosis of reported URL Errors
> 
> 
> I don't know what causes the problem in your case but I can tell how I
> normally track down problems like this:
> 
> use a network sniffer (e.g. ethereal, available on different 
> platforms) and
> record the tcp session between the browser and the webserver when you
> request this particular page. do so again using webtest. then 
> you are able
> to compare the two requests on a low level. things I came 
> across during the
> implementation of my tests:
> 
> - missing cookie (the browser sent a cookie that was set 
> since a long time)
> - browser dependent content (use the header-option to 
> "camouflage" webtest
> respectively httpunit)
> - URL encoding problems (doesn't seem to be problem in your case)
> - 302-redirects: sometimes the response of a GET-request is 
> 302 redirect
> that points to a new location. since the redirect is not 
> noticeable in the
> webtest-report, errors related to such a redirect are hard to detect.
> 
> maybe this helps...
> 
> --luca

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.771 / Virus Database: 518 - Release Date: 9/28/2004