Hi, Patrick.
IIS defines a number of different 401 errors
that indicate a more specific cause of the error. :
401 - Access denied.
401.1 - Logon failed.
401.2 - Logon failed due to server configuration.
401.3 - Unauthorized due to ACL on resource.
401.4 - Authorization failed by filter.
401.5 - Authorization failed by ISAPI/CGI application.
401.7 - Access denied by URL authorization policy on the Web server.
This last error code is specific to IIS 6.0.
It might be that you have to take *those* into consideration
if you want a *specific* error code captured.
I'd try using 401.1 to test catching a "logon failed" exception
Mind you, it could very well be that Windows Integrated Authentication
preempts any IIS authorization scheme.
Maybe testing if the 401 exception works with Forms Authentication would
help us find out if Windows Authentication does preempt IIS's authentication.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
=============== =======
"Patrick Olurotimi Ige" <na********@hot mail.com> wrote in message
news:Oj******** ******@TK2MSFTN GP10.phx.gbl...
Thx Juan for the hint but with the code you posted i can't capture the
HTTPEXCEPTION 401 but exception 404 works if i try browsing an ASPX page
that doesn;'t exist
I have included:-
Case 401
errMessage &= "You are not authorised to view this page."
to loop through but it doesn't seem to work.
I have Windows Integrated
Auth and Basic Auth with a selected DOMAIN.
Any clue why it isn't working?
Thanks
