Today, I will speak about HTTP status codes.
And that's how I found myself writing this little post to you.
"Always look on the bright side of life." 🌔, My mom.
First of all, why do we need a status code?
A status code is a little message from the server that tells you how things went with your request (if everything went well, etc...).
So you can imagine how necessary it is to get feedback on the status of a request.
There are several status codes and each one is dedicated to a specific situation.
The HTTP status codes are divided into 5 different classes defined by the first number they are composed of.
Here is a list of the classes described in the RFC 7231, page 47:
- 1xx: Informational - Request received, continuing process
- 2xx: Success - The action was successfully received, understood, and accepted
- 3xx: Redirection - Further action must be taken in order to complete the request
- 4xx: Client Error - The request contains bad syntax or cannot be fulfilled
- 5xx: Server Error - The server failed to fulfill an apparently valid request
The number one is, of course, the famous:
503 Service Unavailable
The error I had the good fortune to see yesterday appears mainly when the server is busy (overloaded by too many requests ?) or when the server is in maintenance.
It is usually temporary, so be patient!
There is a lot of HTTP status code, so I let you see by yourself here.
As you can see the most frequent status codes are errors 😭😂.
So that's it for this article, like every time, feel free to remind me if I forgot something 😜
I know, I know, you're sad.
But I will come back as soon as possible with other better posts than the previous one. (I hope so)