2xx = ✅
Request was successful.
Request was successful and something new was created based on that request.
Request was received successfully, but may not be acted on immediately.
Request was successful, but information sent to the client about the response comes from a 3rd party server.
Request was successful, but no data is sent back.
Request from the server to reset the information sent, such as form data.
Response to a successful request for only part of a document.
3xx = 👉
Response indicating that what was requested has moved or that there are multiple options that match the request.
Requested document was moved permanently and response contains the URL for that new location. Important to use when changing domains names or URLS of existing documents.
Requested document was temporarily moved to a different location. The URL of the new location is sent
back with the response. 303 and 307 are more specific versions at this type and were implemented as of HTTP/1.1.
Requested document found and responds with the URI where the document can be currently be found.
Requested document has not changed since the last time it was requested. Client loads the document from the cache.
Requested document can only be accessed through a specified proxy.
Requested document can temporarily found at a different URL, which is given in the response. This is a more pure version of what a 302 is normally meant to be.
4xx = ❌
The server did not understand the request.
Client must be authorized before access, typically through some kind of login.
Client does not have permission to access the requested document. If this shows up on a document that should be available, it is likely a permissions issue.
Requested document was not found at the URL give and there is no new location specified for the document. Does not mean that the document is permanently missing from the given URL.
Request method was not allowed for the specified document.
Requested document cannot be sent in a way that the client can understand.
Client must be authorized by the proxy before the requested document can be sent.
Amount of time for the request exceeded the amount of time that the server is set to wait for a request.
Requested document could not be sent because of a conflict in the request.
Similar to a 404, except that it means the document is permanently gone from the URL and there is no new location specified.
Request refused because content length must be specified by client.
At least one condition of the request has failed.
Request was larger than the server was able to handle. A common example of this would be if a File is sent through a posted form and it is larger than the server settings allow tor a post.
The URL was longer than what the server could handle. A URL resulting in this error is normally thousands of characters long, thus it is rarely an issue.
Indicates that the format of at least part of the request is unsupported.
Request could not be fulfilled. Can occur if client requests a part of a document that doesn't exist.
The server could not fulfill the requirements sent in the "Expect" header field.
5xx = ⛔
Generic error message meaning that something broke but nothing more specific can be sent.
Server does not support what is required to fulfill the request.
Server acting as a gateway or proxy received response from an upstream server that was deemed invalid.
Server is currently unavailable due to high load, maintenance, or other temporary situation.
Server acting as a gateway or proxy did not receive response within the amount of time that the server is set to wait for a response.
Server does not support the HTTP protocol used by the client for the request.
- Report issues
- Open pull request with improvements
- Spread the word
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent