Home All Groups Group Topic Archive Search About

<customErrors> confusion

Author
18 May 2006 9:11 PM
Jayyde
New to this so please bear with me...

I set up the:

<customErrors mode="On" defaultRedirect="~/Unavailable.aspx">
</customErrors>



And what it'll do is redirect to the Unavailable.aspx page, but then bring
up ASP errors saying how it can't display what's going on and in order for
it to be able to to set up a <customErrors> tag.  Kind of strange to me
since it's apparently reading it to redirect, but then not using it.  No
clue what's happening here, but any help you gurus can give me will be much
appreciated! =)

Author
19 May 2006 2:39 AM
Jeff Cochran
Show quote Hide quote
On Thu, 18 May 2006 17:11:37 -0400, "Jayyde" <a***@hotmail.com> wrote:

>New to this so please bear with me...
>
>I set up the:
>
><customErrors mode="On" defaultRedirect="~/Unavailable.aspx">
></customErrors>
>
>
>
>And what it'll do is redirect to the Unavailable.aspx page, but then bring
>up ASP errors saying how it can't display what's going on and in order for
>it to be able to to set up a <customErrors> tag.  Kind of strange to me
>since it's apparently reading it to redirect, but then not using it.  No
>clue what's happening here, but any help you gurus can give me will be much
>appreciated! =)

Good question, but has nothing to do with IIS security.  Try a .NET
group, any of those with "dotnet" in them.  And it provides no "ASP
errors" since it's ASP.NET and not ASP.  They are two different
things.

Jeff