Domain checking revisited

This is an old subject, but one that's been bugging me.
 
When we disable Domain Checking (and I understand the reasons why we may want to) some of the pages involved will simply give us an unhandled error, usually "Page not found - vbscript error" or an exception in the .NET version.
 
Probably not a big deal, I just hate to see unhandled errors, even when users type in the browser command line something like "mydomain/forum/editpro.asp". I have no idea why anyone would do that, but it happens (bookmark maybe).
 
So, wouldn't it be good to add an additional request.form check in some of these pages (the ones that give us an unhandled error). Like, in the example of editpro.asp we could add a check for "forumID" as is already done with "jsenabled", like...
 
if request.form("forumID")="" then
response.clear
response.redirect ("goAway.asp")
response.end
end if
 
I just have a fear that some error message thrown up by the server might contain enough clues help hackers.
 
thanks, chief

there is a way better way to trap unhandled errors than adding error handlers everywhere in the code: custom HTTP 500 error handler (just like custom HTTP 404 error handler). You can put a very simple script that captures all unhandled errors and record them in whatever format you want.

Sure, I agree, as long as we follow up our error handling and reporting with error prevention.