Date: 04/13/05 (Asp Dot Net) Keywords: asp, web I'm working on developing custom error pages for a client of ours, and I'm working on trying to have the various errors point to different ASP pages that have scripts that email out to tech support that an error occurred on the website. Obviously the only way (that I know of) to test these error pages is to regenerate the errors. Producing a 404 error is easy, but how would I go about reproducing a 503 (Server Unavailable) error or a 500 (Internal Server Error) error? Also, the way I currently have it set up is that the error pages are all in my /Scripts folder and I was wondering if there was a way to be able to grab the site that the person was trying to go to. So for example someone tries to go to www.fake.com/as9daijoi which doesn't exist. The custom error page comes up, and sends out an email to tech support saying that they were TRYING to navigate to www.fake.com/as9daijoi but couldn't. I have it grabbing their IP address, the time, and any referring pages that there were. Any help would greatly be appreciated. Source: http://www.livejournal.com/community/aspdotnet/32005.html
|