The HTTP status codes are used to indicate that any specific HTTP request has successfully completed or not. The HTTP status codes are categorized into five sections those are listed below:
- Informational responses (100–199)
- Successful responses (200–299)
- Redirects (300–399)
- Client errors (400–499)
- Server errors (500–599)
There are ten Successful Responses those are OK, Created, Accepted, Non-Authoritative Information, No Content, Reset Content, Partial Content, Multi-Status, and Already Reported. All of them are described below:
- 200 OK: The HTTP 200 OK response meaning is that the request made by the client has been successful, but the meaning of the success depending on the four type of request made by the clients. The GET method fetch and transmitted the resources in the message body. The HEAD method is placed in the message body as a entity header. The POST method describing the result of the action is transmitted in the message body, and the last TRACE method contains the request message as received by the server.
- 201 Created: The 201 Created indicates that the request has succeeded and has led to the creation of a resource. It means the origin server MUST create the resource before returning the 201 Created code if that is not possible then it will become 202 Accepted. Basically this HTTP status code indicates that a new resource has been created as a result of the successful completion of a request.
- 202 Accepted: The 201 Accepted indicates that the request from the client has been received, but it does not means the server is working on it. Maybe that time the server is working on other requests, so the client has to wait until the turns of that accepted request come. Accepted means it will definitely proceed.
- 203 Non-Authoritative Information: The 203 Non-Authoritative Information indicates that the request has been received and understood and the information sent back to the client as the response is from a third-party rather than from the original server. The 203 holds a similar value compared to 214, 214 has the advantage of being applicable to responses with any status code.
203 Non-Authoritative Information
- 204 No Content: The 204 No Content indicates that the server has successfully processed the request but needs to return any content or maybe there is no need to send back any data. This code is cacheable by default. Tag header is included in such a response. Best suited as a result of a PUT request which updates the content without changing the current content of the page visible to the client. If the page is gonna change it will become 200 OK.
204 No Content
- 205 Reset Content: The 205 Reset Content is send from the server to the client to request the client that reset the content from which the original document was sent. Like if client is sending the details in a form so need to refresh the UI.
205 Reset Content
- 206 Partial Content: The 206 Partial Content indicates that the server is sending only a part of the requested resource due to a range header sent by the client. There can two situations if the range is one the Content-Type will be the type of the document returned. If there are several ranges then Content-Type is set to multipart/byteranges and each fragment covers one range.
206 Partial Content
- 207 Multi-Status: A multi-status response conveys information about multiple resources where message body is followed by an XML message and contains separate response codes.
- 208 Already Reported: Already Reported used inside of the <dav:propstat> and it response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
Supported Browsers: The browsers compatible with the HTTP status code Successful Responses are listed below:
- Google Chrome
- Internet Explorer
- HTTP headers | Location
- HTTP headers | User-Agent
- HTTP headers | Link
- HTTP headers | Save-Data
- HTTP headers | Content-Type
- HTTP headers | X-Forwarded-Proto
- HTTP headers | X-XSS-Protection
- HTTP headers | X-Frame-Options
- HTTP headers | Last-Modified
- HTTP headers | Date
- HTTP headers | Cookie
- HTTP headers | Strict-Transport-Security
- HTTP headers | Expect
- HTTP | PUT
- HTTP headers | Accept-Encoding
- HTTP headers | Proxy-Authenticate
- HTTP headers | Content-Range
- HTTP headers | Content-Encoding
- HTTP headers | Content-Language
- HTTP headers | X-Content-Type-Options
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.