problem in number HTTP status codes

I think you are almost there.

You have to use HttpWebResponse.StatusCode, which will have a value of OK, Accepted, Redirect, etc. This is an enum and if you need the numerical value, all you have to do is cast it like this:

int code = (int)HttpWebResponse.StatusCode;

If HttpWebResponse.StatusCode == OK, then code == 200.

Soren Madsen

The problem you've got is HTTP is at a lower level within the solution architecture than ASP.Net.

Hyper Text Transport Protocol - The key word is transport. The transport begins within the client internet browser and ends in your ASP.Net application.

ASP.Net is only aware of requests which make it all the way from the client, across the internet, into you hosting network, to your web server and then from your web server to the ASP.Net engine.

HTTP - 500 Internal Server Error

This is often caused by a bad configuration of IIS. If IIS is poorly configured then there's no way the request is going to get from the client to the ASP.Net engine. In which case the request life cycle won't begin, the relevant modules and handlers won't execute and your ASP.Net application including it HttpWebResponse object are going to be completely ignorant.

In IIS you can enable Failed Request Tracing. This will report any bad status codes returned by IIS even if they don't make it to the ASP.Net engine.

http://learn.iis.net/page.aspx/488/using-failed-request-tracing-rules-to-troubleshoot-application-request-routing-arr/[^]

Once you've developed an understanding of the structure of this log you could write code to automatically read the log and report bad statuses in a more convenient way.

IIS also supports a technology called ISAPI (Internet Server Application Programming Interface). ISAPI layers are lower in the solution architecture than the ASP.Net engine.

The following outlines how to write a simple ISAPI layer. It is possible that adding your own ISAPI layer would allow you to capture HTTP status codes which would be missed by the ASP.Net engine but this is not a catch all.

http://blogs.msdn.com/b/rakkimk/archive/2007/03/01/writing-a-simple-isapi-filter.aspx[^]

There are HTTP status codes for timeouts. If the timeout is caused by the clients local ISP then there's no way you're ever going to know about the request or the returned status code.

In a nutshell. You will never get all of the valid statuses listed for a HTTP request/response within the ASP.Net engine as HTTP covers area's well beyond the scope of responsibility of ASP.Net.

For this very reason, the enumerator doesn't need to contain all the HTTP status codes.

This is not an ASP.Net question. The ASP.Net tag is not relevant.

What you're trying to do is check a remote websites availability using the System.Net namespace and the HttpWebRequest object.

Using Wikipedia as a reference of valid HTTP status codes is not a good idea. It lists every company that has ever decided to return a status code which doesn't form part of the HTTP standard.

The enumerator for status code, HttpStatusCode in the HttpWebResponse is every HTTP status code recognised by W3, the owner of the standard.

For the official list of HTTP status code. Please look here:

http://www.w3.org/protocols/rfc2616/rfc2616-sec6.html#sec6.1[^]