A list of common HTTP status codes for production environments

A list of common HTTP status codes for production environments

200-ok , the server successfully returned to the Web page
-standard response for successful HTTP requests.

301-moved Permanently (Permanent jump), the requested page has been permanently redirected to the new location.
-This and all the future requests should is directed to Thegiven.

403-forbidden (no access), the server rejects the request
-Forbidden request (matches a deny filter) = HTTP 403
-the request was a legal request and the server isrefusing to respond to it.

404-not Found, The server could not find the requested page.
-The requested resource could is not being found but could beavailable 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 specificmessage is suitable.

502-bad Gateway (Bad Gateway), typically when the gateway server requests the backend service, the backend service does not return the results correctly as the HTTP protocol.
-the server returned an invalid or incomplete response=> HTTP 502
-The server is acting as a gateway or proxy and Receivedan invalid response from the upstream server.

503-service unavailable (service is not currently available), possibly due to overloading or downtime maintenance.
-No server was available to handle the request = HTTP503
-The server is currently unavailable (because it isoverloaded or down for maintenance).

504-gateway Timeout (gateway Timeout), typically when a gateway server requests a backend service, the backend service does not complete the service at a specific time.
-The server failed to reply in time + = HTTP 504
-The server was acting as a gateway or proxy and do notreceive a timely response from the upstream server.

This article is from the "Study-everyday" blog, make sure to keep this source http://studys.blog.51cto.com/9736817/1597945

A list of common HTTP status codes for production environments