Custom 500 error page......

Im trying to setup a virtual web site that we can use as a "Down for
Maintenance" site that brings down another site and only shows one page
("under construction").

I dont know of a global way of just forwarding all traffic to that one
page (is there a way?) so I just created one document and set it as the
default. However, Id like to start handling other errors (i.e.
bookmarks) to make sure they also go to that one page.

404 works OK, but Im trying to get 500 working. If I try to browse to
a .aspx page that doesnt exist, instead of bouncing to my custom 500
error it gives me the standard 500 internal server error page. The
website is setup without an application space (figured it was
unnecessary because Im just redirecting to a .htm file). In fact when
it was setup with its own application space, the custom errors didnt
work at all for one reason or another.

Any ideas?

Thanks!
-Chris

<charry.TakeThisOut@gmail.com> wrote in message
news:1143560160.093481.224330@t31g2000cwb.googlegroups.com...
: Im trying to setup a virtual web site that we can use as a "Down for
: Maintenance" site that brings down another site and only shows one page
: ("under construction").
:
: I dont know of a global way of just forwarding all traffic to that one
: page (is there a way?) so I just created one document and set it as the
: default. However, Id like to start handling other errors (i.e.
: bookmarks) to make sure they also go to that one page.

If you are actually stopping the main website, and starting an alternate
website, then all you need is a custom 404 error page (404 is "File Not
Found"). This will handle all requests for all files (since no files exist
in this second website).

: 404 works OK, but Im trying to get 500 working. If I try to browse to
: a .aspx page that doesnt exist, instead of bouncing to my custom 500
: error it gives me the standard 500 internal server error page. The
: website is setup without an application space (figured it was
: unnecessary because Im just redirecting to a .htm file). In fact when
: it was setup with its own application space, the custom errors didnt
: work at all for one reason or another.

500 is "Internal Server Error". You should not be generating a 500 simply
because the page doesn't exist (that should generate a 404). So something
else is happening.

Additionally, .NET applications have their custom errors configured in the
web.config file. All other requests (e.g. for static files, or ASP files)
have their custom errors property set in the IIS metabase (you can configure
this via the IIS MMC Snapin)

Cheers
Ken


: Any ideas?
:
: Thanks!
: -Chris
: