Setting Response.Status Generates “HTTP Status String is Not Valid” Exception

Question

I'm writing an HTTP handler in ASP.NET 4.0 and IIS7 and I need to generate a file-not-found condition.

I copied the following code from Mathew McDonald's new book, Pro ASP.Net 4 in C# 2010. (The response variable is an instance of the current HttpResponse.)

response.Status = "File not found";
response.StatusCode = 404;

However, I found that the first line generates the run-time error HTTP status string is not valid.

If, instead of the lines above, I use the following:

response.Status = "404 Not found";

Then everything seems to work fine. In fact, I even see that response.StatusCode is set to 404 automatically.

My problem is that I don't want this to fail on the production server. So I'd feel much better if I could understand the "correct" way to accomplish this. Why did the first approach work for Mathew McDonald but not for me? And is the second approach always going to be reliable?

Can anyone offer any tips?

Answer 1

That's because the Status property is the complete status line sent to the client, not only the message.

You can either write:

response.Status = "404 File not found";

Or, preferably:

response.StatusCode = 404;
response.StatusDescription = "File not found";

Note that, according to its documentation, HttpResponse.Status is deprecated in favor of HttpResponse.StatusDescription.