Online Toolbox
switching mode
tool collection
put it on the desktop
inclusion application
tool search
message response
status code reason phrase representative meaning
100 Continue
(continue)
the client should continue to send the request. this temporary response is used to notify the client that part of its request has been received by the server and has not been rejected. the client should continue to send the remaining part of the request, or ignore the response if the request has been completed. the server must send a final response to the client after the request has been completed.
101 Switching Protocol
(switch protocol)
the server has understood the client's request and will notify the client to use a different protocol to complete the request through the upgrade message header. after sending the last blank line of this response, the server will switch to those protocols defined in the upgrade message header. : similar measures should be taken only when switching to a new protocol is more beneficial. for example, switching to a new http version is more advantageous than an older version, or switching to a real-time and synchronous protocol to deliver resources that take advantage of such features.
successfully responded
status code reason phrase representative meaning
200 OK
(success)
the request is successful. the meaning of success varies according to the method used by the request.
  • get: the resource has been extracted and sent back to the client as a response body.
  • HEAD: entityheadit has been sent back to the client as a response header
  • post: the server processes the data transmitted by the client, and the appropriate resources are transmitted back to the client as a response body.
  • TRACE: serverreceiverequest messagepass back to the client as a response body.
201 Created
(created)
the request is successful, and a new resource has been established according to the request needs. this is usually the response code obtained by the put method.
202 Accepted
(created)
the server has accepted the request, but has not been processed yet. just as it may be denied, the request may or may not be executed eventually. in asynchronous operation, there is no more convenient way to send this status code. : the purpose of returning a 202 status code response is to allow the server to accept requests from other processes (such as a batch-based operation that only performs once a day), without having to keep the client connected to the server until the batch operation is complete. the response to accepting the request processing and returning the 202 status code should include some information in the returned entity indicating the current status of processing, and a pointer to the processing status monitor or status prediction so that the user can estimate whether the operation has been completed.
203 Non-Authoritative Information
(unauthorized information)

the server has successfully processed the request, but the returned entity header meta information is not a valid set of determinations on the original server, but a copy from a local or third party. if it is not the above situation, using 200 status code is the most appropriate.

204 No Content
(no content)
the response has no response content, only response headers, and the response headers may also be useful. the user agent can update the cache information of the corresponding resource based on the new response headers.
205 Reset Content
(reset content)
tell the user agent to reset the document view of the window that sent the request.
206 Partial Content
(some content)
this status code is used when the client uses the range header field to download the file segment
redirect
status code reason phrase representative meaning
300 Multiple Choice
(multiple choices)
there are many possible responses to the request, and the user agent or user must choose one of them. the server has no criteria to follow to select instead of the user.
301 Moved Permanently
(permanently moving)
this status code indicates that the requested uri resource path has changed and the new url will be in response.Location: found in the header field.
302 Found
(temporary move)
this status code indicates that the requested uri resource path has temporarily changed and may continue to change. therefore, the client must continue to use the uri when accessing it in the future. the new url will be in response.Location:found in the header field.
303 See Other
(see other locations)
the server sends the response to guide the client to access another uri using the get method.
304 Not Modified
(unmodified)
tell the client that the requested content has not changed since the last access. the client can obtain the resource directly from the browser cache.
305 Use Proxy
(using a proxy)
the requested resources must be accessed through a proxy. due to security reasons, this status code is not widely supported.
306 unused
(unused)
thisstatus codeno longer used,it was usedexisthttp 1.1 specificationofold versionmiddle.
307 Temporary Redirect
(temporary redirection)

the server sends the response application to guide the client to access another uri using the same method to obtain the resource you want to obtain. the new url will be in the response.Location:found in the header field. it has the same semantics as the 302 status code, and the two accesses must use the same method (get post).

308 Permanent Redirect
(permanent redirection)

the requested resource will be permanently located on another uri. the new url will be in responseLocation:found in the header field. it has the same semantics as the 301 status code, and the two accesses must use the same method (get post).

client error
status code reason phrase representative meaning
400 Bad Request
(error request)
due to the syntax error of the sent request, the server cannot read it normally.
401 Unauthorized
(unauthorized)
you need to authenticate before you can get the requested content, similar to the 403 error. the difference is. after the 401 error, as long as you enter the account password correctly, the verification will be passed.
402 Payment Required
(pay required)
this statuscoderetained withfor future use.create this codethe original purpose wasfornumberused in the payment system,however, it has not been put into use yet.
403 Forbidden
(access is prohibited)
the client has no right to access the requested content, and the server refuses this request.
404 Not Found
(not found)
the server cannot find the requested resource. because this happens frequently, this status code is very common when surfing the internet.
405 Method Not Allowed
(this method is not allowed)
the method used by this request is prohibited by the server, as stipulated in rfc2616, GET andHEAD methods cannot be banned.
406 Not Acceptable
(unacceptable)
in progressserver-driven content negotiationafter that, no appropriate content was found to be passed back to the client.
407 Proxy Authentication Required
(requires proxy authentication)

similar to status code 401, but it needs to pass a proxy to verify.

408 Request Timeout
(request timeout)
the client does not complete a request sending within the server's waiting time. this means that the server will cut off the connection to the client. in other browsers, this response is more common, such as chrome and ie9, which is intended to use the http pre-connection mechanism.speed ​​up browsing. at the same time, note that some servers directly cut off the connection without sending such a response.
409 Conflict
(conflict)
the request conflicts with the current state of the server.
410 Gone
(expired)
the requested resource has been deleted.
411 Length Required
(content length header required)
because the server needs to be in this request Content-Length the header field, but the client did not send it. therefore, the server rejected the request.
412 Precondition Failed
(preprocessing failed)
the server failed to meet the prerequisites set by the client in the request header field when obtaining the resource.
413 Request Entity Too Large
(the request entity is too long)
the requested entity size exceeds the maximum limit set by the server, and the server may close the http link and returnRetry-After header field.
414 Request-URI Too Long
(the request url is too long)
the uri address included by the client request is too long for the server to handle.
415 Unsupported Media Type
(media type does not support)
the server does not support the media type requested by the client, so the request is rejected.
416 Requested Range Not Satisfiable
(the request scope does not meet the requirements)
included in the requestRangethe header field cannot be satisfied, usually becauseRangethe range of numbers in it exceeds the size of the requested resource.
417 Expectation Failed
(expected results failed)
in the request header Expect the expected content specified in the server cannot be satisfied.
418 I'm a teapot
(the server refuses to use a teapot to make coffee)
hyper text coffee pot control protocol (abbreviated as htcpcp) is a protocol made up by the ietf. this protocol is defined in document rfc 2324 (released on april 1, 1998) and is a spoof rfc.
the protocol was designed as an http-like protocol that could be used to control, monitor and diagnose coffee pots, and was later expanded to teapots; the protocol could sometimes be regarded as an early iot experiment.
server-side error
status code reason phrase representative meaning
500 Internal Server Error
(internal server error)
the server encountered unknown unsolvable problems.
501 Not Implemented
(unimplemented)
the server does not support the methods used in the request, for examplePOST andPUT.只有GET andHEADit is a method that stipulates that the server must implement in the rfc2616 specification.
502 Bad Gateway
(gateway error)
the server acts as a gateway and from the upstreamthe server got an invalid http response.
503 Service Unavailable
(service not available)
due to temporary server maintenance or overload, the server is currently unable to process the request. this situation is temporary and will be restored after a period of time. if the delay time can be estimated, the response can include aRetry-After:the header is used to indicate the delay time. if this is not givenRetry-After:in this case, a friendly page for explaining the server problem should be returned, and the cache-related http header information should also be included, because this error usually indicates that the web page should not be cached by the client.
504 Gateway Timeout
(gateway timeout)
the server acts as a gateway and cannot be from the upstreamserverreceive a response in a timely manner and return it to the client.
505 HTTP Version Not Supported
(http version is not supported)
the server does not support the http protocol version used in http requests sent by the client.

HTTP status codeIntroduction

About HTML status codes:

1. In the HTTP protocol, a status code is a set of numbers that represent the status of a server when it responds to a request from a client.

2, the status code is usually divided into the following five categories:

① Informational status code (100-199) : indicates that the server has received the request and is processing it, but has not yet completed it.

② Success status code (200-299) : indicates that the request is successful and the server returns the requested data.

③ Redirect status code (300-399) : indicates that the request has been redirected to another URL.

④ Client error status code (400-499) : indicates that the request contains syntax errors or the request cannot be understood by the server.

Server error status code (500-599) : indicates that the server encountered a problem and could not complete the request.

Internet Business Promoter