HTTP error Code table all HTTP status codes and their definitions.
Code indication
2XX success
200 normal; The request is complete.
201 Normal; Immediately after the POST command.
202 normal; Accepted for processing, but processing is not yet complete.
203 normal; Part of the information-the returned information is only part of it.
204 normal; No response-the request has been received, but there is no information to echo back.
3xx redirection
301 Moved-The requested data has a new location and the change is permanent.
302 found-The requested data temporarily has a different URI.
303 See other-the response to the request can be found under another URI, and the response should be retrieved using the GET method.
304 unmodified-The document was not modified as expected.
305 using a proxy-the requested resource must be accessed through the proxy provided in the Location field.
306 unused-no longer in use; Keep this code for future use.
Errors that occur in the 4XX client
400 Error request-There is a syntax problem in the request, or the request cannot be satisfied.
401 Unauthorized-The client is not authorized to access the data.
402 Payment required-Indicates that the billing system is valid.
403 Forbidden-access is not required even with authorization.
404 Not Found-the server cannot find the given resource; The document does not exist.
407 Proxy authentication Request-The client must first use the proxy to authenticate itself.
415 media type is not supported-the server denies the service request because the format of the requested entity is not supported.
Errors that occur in the 5XX server
500 INTERNAL Error-the server could not complete the request because of an unexpected situation.
501 not executed-the server does not support the requested tool.
502 Error Gateway-server received an invalid response from the upstream server.
503 Unable to get service-the server cannot process the request due to temporary overload or maintenance.
--------------------------------------------------------------------------------------------------------------- --------
HTTP 400-Invalid request
HTTP 401.1-Unauthorized: Logon failed
HTTP 401.2-Unauthorized: Server configuration issues cause logon failure
HTTP 401.3-acl prohibit access to resources
HTTP 401.4-Unauthorized: Authorization denied by filter
HTTP 401.5-Unauthorized: ISAPI or CGI authorization failed
HTTP 403-No access
HTTP 403-access to Internet Service Manager (HTML) is limited to Localhost
HTTP 403.1 Forbidden: Disable executable access
HTTP 403.2-Forbidden: Disable Read access
HTTP 403.3-Forbidden: write-Access Forbidden
HTTP 403.4-No access: SSL required
HTTP 403.5-No access: SSL 128 required
HTTP 403.6-Forbidden: IP address denied
HTTP 403.7-Forbidden: Require client certificate
HTTP 403.8-Forbidden: Prohibit site access
HTTP 403.9-No access: too many users connected
HTTP 403.10-No access: Invalid configuration
HTTP 403.11-No access: Password change
HTTP 403.12-No access: Mapper denied access
HTTP 403.13-No access: Client certificate has been revoked
HTTP 403.15-No access: Too many Client access licenses
HTTP 403.16-Forbidden: Client certificate is untrusted or invalid
HTTP 403.17-Forbidden: Client certificate has expired or is not yet valid
HTTP 404.1-Unable to find Web site
HTTP 404-File not Found
HTTP 405-Resource is forbidden
HTTP 406-Unacceptable
HTTP 407-Proxy Authentication Required
HTTP 410-Never available
HTTP 412-Prerequisite failure
HTTP 414-Request-URI too long
HTTP 500-Internal server error
HTTP 500.100-Internal Server error-ASP error
HTTP 500-11 Server shutdown
HTTP 500-12 Application Restart
HTTP 500-13-Server Too busy
HTTP 500-14-Application not valid
HTTP 500-15-Request Global.asa not allowed
Error 501-Not implemented
HTTP 502-Gateway Error ===================================================
502 Bad Gateway cause analysisSubmitting the request to the gateway, such as PHP-FPM, is performed, but for some reason the PHP-FPM process terminates execution because it has not been executed. In this case, the problem is very clear, and the gateway services such as the configuration of PHP-FPM.
There are two parameters in the php-fpm.conf configuration file that you need to consider, namely Max_children and Request_terminate_timeout.
Max_children the maximum number of child processes, the maximum number of responses to PHP-FPM is reached at high concurrent requests, and 502 errors will occur for subsequent requests. You can view the current number of connections by using the netstat command.
Request_terminate_timeout sets the time-out for a single request to expire. You should also note the Max_execution_time parameter in php.ini. The 502 error also occurs when the request is terminated.
When you accumulate a large number of PHP requests, you restart PHP-FPM release resources, but a two minutes less, 502 again to present, what is the cause of this? At this point should also consider the database, to see whether the database process has a large number of locked processes, the database deadlock caused the timeout, the front end of the continuation of the request, but the SQL statement is still waiting to release the lock, this time will restart the database service or kill to kill the deadlock SQL process.
504 Gateway time-out cause analysisThe 504 error is generally related to the nginx.conf configuration. Mainly related to the following parameters: Fastcgi_connect_timeout, Fastcgi_send_timeout, Fastcgi_read_timeout, Fastcgi_buffer_size, Fastcgi_ Buffers, Fastcgi_busy_buffers_size, Fastcgi_temp_file_write_size, Fastcgi_intercept_errors. In particular, the first three timeout periods. If the fastcgi buffer is too small it will cause the fastcgi process to be suspended and thus evolve to a 504 error.
HTTP Error Code table
