- Status codes
- 200
- 200 - ok
- 200 ok means everything went well on the server side.
- 201 - created
- create is another thumbsup when something new was created
- 204 - No content
- it means when we delete a sent data it means that that task is done and it worked there is no data to send back.
- 400
- 400 - something went wrong
- here the server says that check what data is sent
- 400 - bad request
- something in the request doesn’t make sense
- 401 - unauthorized
- it means we are missing the right credentials
- 403 - forbidden
- giving access to only the privileged
- 404 - Not found
- request file is not there
- 429 - to many requests
- server letting you know that slow down we are sending requests too fast and hitting rate limits for busy apis
- 500
- 500 - internal server error
- these errors require deeper investigation. they are not easy to spot. we need to dig into server logs to find what is wrong
- 502 - bad gateway
- this hints issues between servers, like a proxy failing to get a response. example - using nginx as a reverse proxy and it can’t get a valid response from the application server this could be due to server overloads, network glithes or just miscofiguration.
- 503 - service unavailable
- the server cannot handle requests rightnow due to maintenance or traffic overload.