Common server request status codes
Server status codes and their meanings:
- 200: The server is responding normally.
- 304: The resource has not been modified since the last request (this is usually used in the browser's caching mechanism, especially when using GET requests).
- 400: The requested resource could not be found.
- 401: Insufficient permission to access the resource.
- 403: Not authorized to access resource.
- 404: The resource to be accessed does not exist.
- 405: The resource to be accessed is forbidden.
- 407: The accessed resource requires proxy authentication.
- 414: The requested URL is too long.
- 500: Internal server error.
Complete server status code :
- 100 - Client must continue making requests
- 101 - The client asks the server to convert the HTTP protocol version according to the request
- 200 - successful transaction
- 201 - Prompt to know the URL of the new file
- 202 - Accepted and processed, but processing not completed
- 203 - Return information is uncertain or incomplete
- 204 - The request was received, but the return information was empty
- 205 - The server has completed the request, the user agent MUST reset the currently viewed file
- 206 - The server has completed the GET request of some users
- 300 - The requested resource is available in multiple places
- 301 - delete request data
- 302 - Request data found at other address
- 303 - Advise customers to visit other URLs or access methods
- 304 - The client has performed a GET, but the file has not changed
- 305 - The requested resource must be obtained from the address specified by the server
- 306 - code used in the previous version of HTTP, no longer used in the current version
- 307 - Declare the temporary deletion of the requested resource
- 400 - Bad request, such as syntax error
- 401 - Request authorization failed
- 402 - keep a valid ChargeTo header response
- 403 - request not allowed
- 404 - No file, query or URL found
- 405 - The method defined by the user in the Request-Line field is not allowed
- 406 - According to the Accept drag sent by the user, the requested resource is not accessible
- 407 - Similar to 401, the user must first be authorized on the proxy server
- 408 - The client did not complete the request within the time specified by the user
- 409 - The request cannot be completed for the current resource state
- 410 - The resource is no longer on the server and there is no further reference
- 411 - The server rejected the request for the user-defined Content-Length attribute
- 412 - One or more request header fields are incorrect in the current request
- 413 - The requested resource is larger than the size allowed by the server
- 414 - The requested resource URL is longer than the server allows
- 415 - The requested resource does not support the requested item format
- 416 - The request contains the Range request header field, there is no range indication value within the current request resource range, and the request does not contain the If-Range request header field
- 417 - The server does not meet the expected value specified by the request Expect header field. If it is a proxy server, it may be that the next-level server cannot meet the request.
- 500 - The server generated an internal error
- 501 - The server does not support the requested function
- 502 - The server is temporarily unavailable, sometimes to prevent system overload
- 503 - Server overloaded or suspended for maintenance
- 504 - The gateway is overloaded, the server uses another gateway or service to respond to the user, and the waiting time is set longer.
- 505 - The server does not support or refuses to support the HTTP version specified in the request header