Hi, We have configured firewall policies in our ISA 2004 server to block any http payloads greater than a certain limit within the http config options. This works fine, but displays a http 500/ISA 12217 error to the user when they hit this limit. 1. How do we publish a more personalised error page to the user? 2. Does this involve setting up a static page in place of the 12217 page within ISA? If so, presumably this will display this page if any 12217 errors are detected by ISA? 3. Is there a way to determine what the possible 12217 errors refer to? Thanks in advance!
If you look in your ISA's installation folder you should see a sub-folder called \ErrorHtmls which contains the entire HTML error pages (error number is referenced in the filename) that ISA displays on an error generating event. You can modify these error pages as needed.
David Melvin Ohio MCSE: Security 2003, MCSA:Security 2003
2. Does this involve setting up a static page in place of the 12217 page within ISA? If so, presumably this will display this page if any 12217 errors are detected by ISA? 3. Is there a way to determine what the possible 12217 errors refer to?
The 12217 error should be in reference to the HTTP filter rejecting the request and ISA should be calling the default.htm error page.
I have done some basic tests in the errorhtml folder and created a new 12217.htm and 12217r.htm and can get it to display a customised html page (it seems to use 12217r.htm).
Although a majority of the time it will be displayed when a user exceeds the payload limit, it could be as a rejection of other aspects of the http filter so I will issue an error message stating some of the possible problems (i.e. http payload size, url length, executable/signature errors etc.). Does this seem a reasonable approach - is there anything else I should consider when doing this?
This was just the sort of info I was looking for too. Is is possible though to redirect to error pages hosted on a website elsewhere and pass through the full error information from the ISA? I wanted to do some more radical changes to the error reporting pages and it would be more convenient if I could host the whole thing off the ISA.