Thanks for the response, I understand that ASP.NET will not be able to
handle this error, is there another way to redirect a 401.3 error to a
custom error page? I tried redirect in IIS under the custom error tag for
the webpage, but that didn't work, it still shows the ASP.NET generated
401.3 error page.
"Jim Cheshire [MSFT]" <> wrote in message
news:...
> Hi Tony,
>
> You cannot do this. The 401.3 is handled prior to ASP.NET's ISAPI filter
> having the opportunity to do anything with it.
>
> Jim Cheshire [MSFT]
> MCP+I, MCSE, MCSD, MCDBA
> Microsoft Developer Support
>
>
> This post is provided "AS-IS" with no warranties and confers no rights.
>
> --------------------
> >From: "tony" <test>
> >Subject: 401.3 error redirecting
> >Date: Thu, 19 Aug 2004 10:43:42 -0700
> >Lines: 8
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
> >Message-ID: <>
> >Newsgroups: microsoft.public.dotnet.framework.aspnet
> >NNTP-Posting-Host: 207-213-137-145.ded.pacbell.net 207.213.137.145
> >Path:
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP12
> phx.gbl
> >Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet:256245
> >X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
> >
> >I've been searching through the threads to find a solution for 401.3
error
> >triggered by windows authentication not being able to redirect to a
custom
> >error page to no avail. It seems that ASP.NET does not redirect 401
errors
> >yet changing the Custom Errors redirect in IIS does not help either. Has
> >anyone found a solution to this problem? Seems like it should be a
> commonly
> >encountered problem. Any help will be greatly appreciated.
> >
> >
> >
>
Similar Threads
