Exception Handling (6), HttpStatusCode

Exception handling is required in any application. It is a very interesing issue where different apps have their own various way(s) to handle that. I plan to write a series of articles to discuss this issue

• Exception Handling (1), in ASP.NET MVC
• Exception Handling (2), in ASP.NET Web API
• Exception Handling (3), in ASP.NET Core MVC
• Exception Handling (4), in ASP.NET Core Web API
• Exception Handling (5), in ASP.NET Summary 
• Exception Handling (6), HttpStatusCode --- this article

This article is information collection for HttpStatusCode.

The HttpStatusCode is used in ASP.NET Web API:

HttpStatusCode Enum (System.Net) | Microsoft Learn

 

Click the Graph to view details:

HTTP response status codes

HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:

1. Informational responses (100 – 199)
2. Successful responses (200 – 299)
3. Redirection messages (300 – 399)
4. Client error responses (400 – 499)
5. Server error responses (500 – 599)

The status codes listed below are defined by RFC 9110.

References

• HttpStatusCode Enum (System.Net) | Microsoft Learn
• HTTP Status Codes (restapitutorial.com)
• HTTP response status codes - HTTP | MDN (mozilla.org)
• List of HTTP status codes - Wikipedia
• HTTP - Status Codes (tutorialspoint.com)