|
|
submitted by
ColinCochrane
8 months, 16 days ago
colincochrane.com — Defining custom error pages is a convenient way to show users a friendly page when they encounter an HTTP error such as a 404 Not Found, or a 500 Server Error. Unfortunately ASP.NET handles custom error pages by responding with a 302 Temporary redirect to the error page that was defined. In this post I explain how to create a custom HttpModule that allows you to use custom error pages while preserving the original HTTP status code and avoiding the 302 redirect to the error page.
|
|
tags:
ASP.NET | tag it
Everyones tags: | Your tags: | |
|
|
|
Add a live kick counter to your blog >>
You can even customize the image by choosing your own colors, and then clicking
the button below to update the preview and the html code:
Simply copy and paste this HTML into your blog post.
Users who kicked this story:
No comments so far
|