|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Custom ErrorsHi there,
Is it possilbe to redirect error pages (401, 404, etc), to a custom page using ASP/VBScript. I'd rather not use the custom errors tab in IIS as we have more than one web site running on the IIS server. Thanks very much/... Forgot to say that I know you can define different error pages per virtual
directory, but would prefer, if possible, to do as asked above!! Thanks/... Show quoteHide quote "Andy Smith" wrote: > Hi there, > > Is it possilbe to redirect error pages (401, 404, etc), to a custom page > using ASP/VBScript. > > I'd rather not use the custom errors tab in IIS as we have more than one web > site running on the IIS server. > > Thanks very much/... Hi,
This is not possible (AFAIK) using ASP. Either change the settings via IIS Manager, use ISAPI Filter, or convert to ASP.NET (where you can specify changes via web.config). If you have access to the server, you can script the necessary changes (using ADSI) to the metabase, so I don't really understand the argument about having "lots of sites" as an impediment to doing this. Cheers Ken Show quoteHide quote "Andy Smith" <AndySm***@discussions.microsoft.com> wrote in message news:507F4C28-E9CA-4538-A63C-E4E02E0E6EA6@microsoft.com... : Forgot to say that I know you can define different error pages per virtual : directory, but would prefer, if possible, to do as asked above!! : : Thanks/... : : "Andy Smith" wrote: : : > Hi there, : > : > Is it possilbe to redirect error pages (401, 404, etc), to a custom page : > using ASP/VBScript. : > : > I'd rather not use the custom errors tab in IIS as we have more than one web : > site running on the IIS server. : > : > Thanks very much/... This is how to "redirect" error pages to custom page handlers.
Use the custom error tab in IIS at the global (or website) level (so that its settings inherit down to child nodes [unless you specifically override them), and set up each custom error in the tab to directly call your own custom page via a single URL. i.e. You have a custom error page located at: /bin/CustomErrors.asp You change IIS custom errors at the global level to map all custom error handlers to URL of /bin/CustomErrors.asp Now, every single error that happens on IIS will be routed through /bin/CustomErrors.asp. Except for the 401 errors. -- //David IIS http://blogs.msdn.com/David.Wang This posting is provided "AS IS" with no warranties, and confers no rights. // "Andy Smith" <AndySm***@discussions.microsoft.com> wrote in message Is it possilbe to redirect error pages (401, 404, etc), to a custom pagenews:05EB6D4B-22E1-4B64-B8E4-300D591E1534@microsoft.com... Hi there, using ASP/VBScript. I'd rather not use the custom errors tab in IIS as we have more than one web site running on the IIS server. Thanks very much/... 
Other interesting topics
AD Custom App Pool identity, Custom IUSR identity, and a lot more.
IIS 6 on Win2003 with SP1 RE: Virtual Directory mapped to Netware server in IIS6 fails Problem with the "Too many users logged" New SSL Certificate not showing on browsers? does w2k3 server automatically change user's settings based on time? IIS / OWA Cookie problem with ShowModalDialog and window.open Basic Authentication - Sometimes No Prompt Integrated Windows Authentication on a member server |
|||||||||||||||||||||||
