Hi Ben,

with FF you have the header
WWW-Authenticate: Basic realm="default"
which seems correct.

Can you look at the headers received using WebTest? (Look at
#WebTest#/lib/log4j.properties to configure the log).

Marc.

[EMAIL PROTECTED] wrote:
> 
> Hi Mark thanks for your response.
> 
> Yes this was my initial guess at the problem after 
> examining the headers a couple of days ago and seeing only the
> 'Basic' token and no realm="foo" parameter. So I changed the 
> <login-config> details to contain the default realm definition but 
> unfortunately received exactly the same error. Below is the
> request/response headers
> I saved using livehttpheader :-
> 
> http://localhost:7001/ros.bops.presentation.ui/ros/bops/presentation/ui/
> workflow/pageflows/begin.do
> 
> GET
> /ros.bops.presentation.ui/ros/bops/presentation/ui/workflow/pageflows/be
> gin.do HTTP/1.1
> Host: localhost:7001
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.3)
> Gecko/20070309 Firefox/2.0.0.3
> Accept:
> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plai
> n;q=0.8,image/png,*/*;q=0.5
> Accept-Language: en-gb,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 300
> Connection: keep-alive
> Cookie:
> JSESSIONID=dQpdG5KD1g22ytYt13tNq31fhWy8fTWrbTtpw3v5Tr2nCx1m4p4q!13979745
> 74;
> ADMINCONSOLESESSION=qjtwG5HZnyvY1w86JsPqxLJTxwpH8QztTG6FsmkKSNLHpRPSnj46
> !-442889654
> 
> HTTP/1.x 401 Unauthorized
> Connection: close
> Date: Wed, 08 Aug 2007 13:53:54 GMT
> Content-Length: 1518
> Content-Type: text/html
> WWW-Authenticate: Basic realm="default"
> X-Powered-By: Servlet/2.4 JSP/2.0
> ----------------------------------------------------------
> 
> Cheers,
> 
> Ben
> 
> 
> 
> --__--__--
> 
> Message: 5
> Date: Tue, 07 Aug 2007 13:07:18 +0200
> From: Marc Guillemot <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: Re: [Webtest] Basic authentication
> Reply-To: [email protected]
> Reply-To: Marc Guillemot <[EMAIL PROTECTED]>
> 
> Hi Ben,
> 
> looking quickly at the source of the AuthChallengeParser, it seems that
> it await more information in the challenge string than only "Basic".
> 
> Does it occurs each time? I could imagine that the server sent a bad
> response and that WebTest directly failed where "normal" browsers retry.
> 
> Can you sniff the Http traffic in a normal browser (for instance using
> the liveHttpHeader add-on for Firefox) to "see" what happens there?
> 
> Marc.


-- 
Blog: http://mguillem.wordpress.com

_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to