Home/ Questions/Q 36205
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T14:21:24+00:00

I am implementing a HttpRequestValidationException in my Application_Error Handler, and if possible, I want

  • 0

I am implementing a HttpRequestValidationException in my Application_Error Handler, and if possible, I want to display a custom message.

Now, I’m thinking about the StatusCode. In my current example, it sends a 200, which I think should not be done. I would like to send the (IMHO) more appropriate 400 Bad Request instead. However, at the same time, I would like to use Response.Write to enter a custom message. Firefox displays it properly, but IE7 gives me the Default unhelpful Internet Explorer Error Page.

On one side, I guess that Internet Explorer just assumes that everything <> 200 is simply not having any "good" content, and the RFC is not really clear here.

So I just wonder, is sending a HTTP 200 for an Error Page caused by a HttpRequestValidationException good practice or not? Are there good alternatives?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. An HTTP 200 Response Code does not indicate an error. It indicates that everything was OK. You should not use a 200 response code for an error.

    Internet Explorer shows its ‘Friendly Errors’ page if the response is less than 512 bytes. Here’s more on this issue: http://weblogs.asp.net/scottgu/archive/2006/04/09/442332.aspx,

    • 0