top of page
  • Writer's pictureRahul R

What are HTTP response status codes as per RFC 7231

HTTP status codes are standard response codes given by web site servers on the internet. They are standardized by the Internet Engineering Task Force (IETF) as a part of the HTTP protocol specification, RFC 7231.

The HTTP status codes are grouped into five categories:

  1. Informational responses (100–199)

  2. Successful responses (200–299)

  3. Redirects (300–399)

  4. Client errors (400–499)

  5. Server errors (500–599)

Here is a brief explanation of each category:

  1. Informational responses (100–199): These are provisional responses indicating that the client's request has been received and understood, but that the server has not yet completed its actions.

  2. Successful responses (200–299): These indicate that the server has successfully received, understood, and accepted the client's request.

  3. Redirects (300–399): These indicate that the client must take additional action to complete the request.

  4. Client errors (400–499): These indicate that there was an error in the client's request.

  5. Server errors (500–599): These indicate that the server was unable to complete the request.

Some commonly used HTTP status codes in APIs include:


Successful 2xx

  • 200 OK

  • 201 Created

  • 202 Accepted

  • 203 Non-Authoritative Information

  • 204 No Content

  • 205 Reset Content

Redirection 3xx

  • 300 Multiple Choices

  • 301 Moved Permanently

  • 302 Found

  • 303 See Other

  • 305 Use Proxy

  • 306 (Unused)

  • 307 Temporary Redirect

Client Error 4xx

  • 400 Bad Request

  • 402 Payment Required

  • 403 Forbidden

  • 404 Not Found

  • 405 Method Not Allowed

  • 406 Not Acceptable

  • 408 Request Timeout

  • 409 Conflict

  • 410 Gone

  • 411 Length Required

  • 413 Payload Too Large

  • 414 URI Too Long

  • 415 Unsupported Media Type

  • 417 Expectation Failed

  • 426 Upgrade Required

Server Error 5xx

  • 500 Internal Server Error

  • 501 Not Implemented

  • 502 Bad Gateway

  • 503 Service Unavailable

  • 504 Gateway Timeout

  • 505 HTTP Version Not Supported

17 views0 comments

Recent Posts

See All

How to setup reverse proxy on apache2

To set up a reverse proxy to a local installation using Apache2, you need to configure the Apache Virtual Hosts to forward requests to your local server. Here's a step-by-step guide: Enable Proxy Modu

How to Set Up Odoo with Apache Reverse Proxy on Ubuntu

Welcome, adventurous souls, to the whimsical world of Odoo installation! In this zany tutorial, we'll embark on a wild journey to set up Odoo, the beloved open-source ERP software, with an Apache reve

How to Attach S3 to your Django Project

Install Required Packages: Install django-storages package, which provides support for various storage backends including Amazon S3. You can install it via pip: pip install django-storages Configure D

Comments


bottom of page