ASP.NET Custom Errors: Preventing 302 Redirects To Custom Error Pages(colincochrane.com)

submitted by ColinCochraneColinCochrane(235) 4 years ago

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.

add a comment |category: |Views: 200

tags: another

new Add a live kick counter to your blog >> liveImage

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:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

No comments so far

information Login or create an account to comment on this story