Want to hire a development team?
No Images Added Yet

Create a Custom ASP Error Page

Rated3.0/5 (1 ratings)
Add to Favorites
Publisher
Learn to create a centralized error page to display custom errors.
Product Details

In this tutorial, you will learn how to assign custom errors to common problems that you may experience with your web site and create a centralized error page to display custom errors.

Report this Listing
Price
Free
Licence Type
Free
Views
3,250
Submitted on
13th February 2000
Last Updated
11th February 2009
Advertisement The banner below is an advertisement
Quikwit - AI Chatbot Platform

You May Also Like

Cloud Services You May Like

Cloudflare Ongoing Management & Monitoring (Monthly)

Monthly Cloudflare management including policy changes, monitoring, tuning and issue response.

Automating AWS Server Backups and configuring AWS Backup Cycles and AWS Backup rules

Set up automated backups for AWS servers using AWS Backup and clear backup cycles.

Monitoring Spot Instance Prices and Migrating Instances to Optimal Types/Regions

Automatically monitoring AWS Spot instance prices and moving servers to better instance types or regions for maximum sav

AWS Backup and Restoration Service for Instances

Backup and restore your AWS instances to protect data, recover from failures, and ensure business continuity.

User Reviews

Please rate the listing and tell the world know what do you think about the listing.
(1 ratings)
Average User Rating: 3.0/5
The code is neat, but......
Reviewed byAnonymousonThu, 10th January 2002
Rating 3 - Average
The code to handle customer errors is neat, but it will solve only one problem. The reason being the respose.redirect must be presented before the HTML is sent to the browser. But in the actual scenario, the error may occur at any point in a page. In this case, it will not get redirected at all. Another thing is, there is no way we can specify the standard error page so that whenever an error occurs at any point in a page, the ASP engine will simply redirect to it. The only way to solve this is to issue a response.Buffer = true at the top of every page and then whenever an occurs, one can trap it and redirect it to a standard error page by issuing response.redirect followed by response.flush. This will redirect at any point in a page.
Displaying 1-1 out of 1 reviews
View All Reviews