Common HTTP status codes in the production environment

Common HTTP status codes in the production environment

The List of common HTTP status codes in the production environment is:

200-OK. The server returns the webpage successfully.
-Standard response for successful HTTP requests.

301-Moved Permanently (permanent jump), the requested webpage has been Permanently redirected to a new location.
-This and all future requests shocould be directed to the given.

403-Forbidden (Access prohibited), the server rejects the request
-Forbidden request (matches a deny filter) = & gt; HTTP 403
-The request was a legal request, but the server is refusing to respond to it.

404-Not Found: the server cannot find the requested page.
-The requested resource cocould not be found but may be available again in the future.

500-Internal Server Error (Internal Server Error)
-Internal error in haproxy => HTTP 500
-A generic error message, given when no more specific message is suitable.

502-Bad Gateway (Bad Gateway). Generally, when the Gateway server requests a backend service, the backend service does not return the correct result according to the http protocol.
-The server returned an invalid or incomplete response => HTTP 502
-The server was acting as a gateway or proxy and received ed an invalid response from the upstream server.

503-Service Unavailable (the Service is currently Unavailable), which may be maintained due to overload or downtime.
-No server was available to handle the request => HTTP 503
-The server is currently unavailable (because it is overloaded or down for maintenance ).

504-Gateway Timeout (Gateway Timeout). Generally, when a Gateway server requests a backend service, the backend service does not complete the service within a specified period of time.
-The server failed to reply in time => HTTP 504
-The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.