IIS 5 & IIS 6
Error Mapping Properties
Last post Mar 03, 2009 08:17 AM by tomkmvp
Mar 02, 2009 03:02 PM|Paxxer|LINK
I'm setting the custom error pages on a website running on Windows XP, IIS 5.1.
I open the properties for the Web Site, got to the Custom Errors tab, Select one of the HTTP Error type, the click on "Edit Properties", and I only have [Default and File] available in the Message Type drop down.
All of the documentation says there should be a URL option in that drop down. I am unable to set the error pages to an aspx page in the website.
Here's a screen shot:
Error Mapping Properties
Mar 02, 2009 05:19 PM|tomkmvp|LINK
IIRC, you can't have a URL for this one because it would cause a looping condition - the URL would have to be https in order to not generate the error.
Mar 02, 2009 05:23 PM|Paxxer|LINK
Thank you for the reply.
But I am not specifically asking about the 403 error. I am asking why is the URL option missing? It is missing from all of the error codes.
Take a look at your interface. The interface isn't "smart" enough to know that this would cause a looping condition.
Actually I was thinking of an error page like this for the 403 error.
This should handle the circular reference issue, and allow my users to browse to a secure page seemlessly. But I need to figure out why the URL option is missing.
Mar 02, 2009 11:19 PM|Paxxer|LINK
I found the solution!
1) I went to another server with a new web application on it.
2) I wanted to confirm that the URL option was there on that server, and that something was amiss with the server I was working on
3) When I opened the Error Mapping Properties for the 403.x error, only the Default and File options were present on this other server.. hmmm
4) So I figured, this can't be, as I couldn't find anything on the Web about this issue.
5) So I did the user click click click on the other codes, in higher numbers, and after a couple clicks there was the
6) I went back to the 403.x and sure enough the URL option came up.
Came back to the original server,did the same, sure enough there was the URL option.
FYI, the SSLRedirect.aspx page that i mention in the above post works like a champ. IIS takes care to send a request that should be secure (as configued in IIS) to this aspx page. Then the page, simple changes the http to https and tries again, and this
time it goes through securely. This way I can have most of my site, unsecure, and faster, and only the logon, password, etc pages need to require SSL. Then leaving these pages, I programatically change the https back to http.
Mar 03, 2009 08:17 AM|tomkmvp|LINK
Yes my mistake - good job sorting this out.