This is the 20th day of my participation in the August Text Challenge.More challenges in August

1 the beginning 📌

This type of status code indicates that the request has been accepted and needs to continue processing. This type of response is a temporary response, containing only the status line and some optional response header information, and ending with an empty line. Since no 1XX status code is defined in the HTTP/1.0 protocol, the server forbids sending 1XX responses to such clients except under certain test conditions. These status codes represent responses that are informational and indicate other actions the customer should take.

1XX - Message prompt · 100 - Continue The original request has been accepted and the customer should Continue to send the rest of the request. · 101-switching Protocols Server converts to another protocol in compliance with a client's request (HTTP 1.1 new)Copy the code

2 the beginning 📌

! [insert picture description here] (img – blog. Csdnimg. Cn/e6f89183e2a… =500x)

This type of status code indicates that the request has been successfully received, understood, and accepted by the server.

2xx - Success · 200 - OK Everything is fine, reply documents for GET and POST requests follow. · 201-created server has Created the document and the Location header gives its URL. · 202-ACCEPTED The request has been Accepted, but processing is not yet complete. · The 203-non-authoritative Information document has returned normally, but some of the reply headers may not be correct because a copy of the document is used, non-authoritative Information (new in HTTP 1.1). · 204-no Content There is No new document, the browser should continue to display the original document. This status code is useful if the user refreshes the page periodically and the Servlet can determine that the user document is sufficiently new. · 205-reset Content There is no new Content, but the browser should Reset what it shows. Used to force the browser to clear form input (new in HTTP 1.1). · 206 - Partial Content The client sends a GET request (block request) with a Range header, and the server completes it (new in HTTP 1.1).Copy the code

📌 3 at the beginning

The client browser must do more to fulfill the request. For example, the browser might have to request a different page on the server, or repeat the request through a proxy server.

The document requested by the customer can be found in Multiple locations that are already listed in the returned document. If the server wants to propose a preference, it should be indicated in the Location reply header. · 301-Moved Permanently The document requested by the Permanently customer is elsewhere, the new URL is given in the Location header, and the browser should automatically access the new URL. · 302-FOUND is similar to 301, but the new URL should be considered a temporary replacement, not permanent. Note that the corresponding status message in HTTP1.0 is "Moved Temporatily". When this status code appears, the browser can automatically access the new URL, so it is a useful status code. Note that this status code can sometimes be substituted with 301. For example, if the browser incorrectly requests http://host/~user (missing the trailing slash), some servers return 301 and others 302. Strictly speaking, we can only assume that the browser automatically redirects only when the original request is a GET. For details, see 307. · 303/see Other is similar to 301/302, except that if the original request was POST, the redirected target document specified by the Location header should be extracted via GET (new in HTTP 1.1). · 304-Not Modified The client has a buffered document and makes a conditional request (typically providing an if-Modified-since header to indicate that the client only wants to update the document after the specified date). The server tells the client that the originally buffered document can still be used. · 305-Use Proxy The document requested by the client should be retrieved through the Proxy server specified in the Location header (new in HTTP 1.1). · 307-temporary Redirect is the same as 302 (Found). Many browsers mistakenly redirect in response to a 302 reply, even though the original request was A POST, and even though it can actually redirect only if the reply to a POST request is 303. For this reason, HTTP 1.1 added 307 to make it easier to distinguish between several status codes: browsers can follow redirected GET and POST requests when a 303 reply occurs; If the answer is 307, the browser can only follow the redirection of the GET request. (New in HTTP 1.1)Copy the code

📌 4 beginning

An error occurred. The client seems to have a problem. For example, if a client requests a page that does not exist, the client does not provide valid authentication information.

4xx - Client error · 400 - Bad Request Syntax error occurs in the Request. · 401 - Unauthorized Access Is denied. A customer attempts to gain Unauthorized access to a password-protected page. The response contains a www-Authenticate header, which the browser uses to display the user name/password dialog box and re-issue the request after filling in the appropriate Authorization header. IIS defines a number of different 401 errors that specify more specific causes of the error. These specific error codes are displayed in the browser, but not in the IIS logs: · 401.1 - Login failed. · 401.2 - Login failed due to server configuration. · 401.3 - Not authorized due to ACL resource restrictions. · 401.4 -- Filter authorization failed. · 401.5 - ISAPI/CGI application authorization failed. · 401.7 -- Access denied by URL authorization policy on Web server. This error code is specific to IIS 6.0. · 403-forbidden Resources are unavailable. The server understands the client's request, but refuses to process it. This is usually caused by permission Settings on files or directories on the server. Access forbidden: IIS defines a number of different 403 errors that specify the more specific cause of the error: · 403.1 - Execution access forbidden. · 403.2 -- Read access is disabled. · 403.3 -- Write access is disabled. · 403.4 -- SSL required. · 403.5 -- SSL 128 is required. · 403.6 - IP address was rejected. · 403.7 -- Client certificate required. · 403.8 -- Site access denied. · 403.9 -- Too many users. · 403.10 - Invalid configuration. · 403.11 -- Password change. · 403.12 -- Access to the mapping table is denied. · 403.13 - The client certificate is revoked. · 403.14 - Reject directory list. · 403.15 - Exceeds client access permission. · 403.16 - Client certificate is not trusted or invalid. · 403.17 - Client certificate has expired or has not taken effect. · 403.18 - The requested URL cannot be executed in the current application pool. This error code is specific to IIS 6.0. · 403.19 - CGI cannot be executed for clients in this application pool. This error code is specific to IIS 6.0. · 403.20 - Passport login failed. This error code is specific to IIS 6.0. · 404-not Found The resource at the specified location could Not be Found. This is also a common response. · 404.0 - (None) -- No files or directories found. · 404.1 - The Web site cannot be accessed on the requested port. · 404.2 - Web services extended locking policy prevents this request. · 404.3 - MIME mapping policy blocks this request. · 405-method Not Allowed Request methods (GET, POST, HEAD, DELETE, PUT, TRACE, etc.) are Not applicable to specified resources. The HTTP predicate used to access this page is Not allowed (methods are Not allowed) (HTTP 1.1 new) · 406 - Not Acceptable The specified resource has been found, but its MIME type is Not compatible with that specified by the customer in the Accpet header. The client browser does not accept the MIME type of the requested page (new in HTTP 1.1). · 407-proxy Authentication Required requires Proxy Authentication, similar to 401, indicating that the customer must first be authorized by the Proxy server. (HTTP 1.1新) · 408-request Timeout The client does not send any Request within the server permission waiting time. The customer can repeat the same request at a later date. · 409-Conflict is usually associated with PUT requests. The request cannot succeed because it conflicts with the current state of the resource. · 410-GONE The requested document is no longer available, and the server does not know which address to redirect to. It differs from 404 in that returning 407 means the document is permanently removed from the specified location, whereas 404 means the document is unavailable for unknown reasons. · 411-Length Required The server cannot process requests unless the client sends a Content-Length header. · 412-Preconditions specified in the request header fail (HTTP 1.1 new). · 413 -- Request Entity Too Large The size of the target document is larger than the server is currently willing to process. If the server thinks it can process the request later, it should provide a retry-after header (new in HTTP 1.1). · 414 - Request URI Too Long URI Too Long (new in HTTP 1.1). · 415 -- Unsupported media types. · 416 -- Requested Range Not Satisfiable server cannot satisfy the Range header specified in the request. (NEW in HTTP 1.1) · 417 -- Execution failed. · 423 -- Locking error.Copy the code

5 the beginning 📌

An error or exception occurs when the server processes a request. The server may realize that it cannot process the request with the current hardware or software resources. Unless this is a HEAD request, the server should contain an explanation entity that explains the current error state and whether the state is temporary or permanent. The browser should show the user any entities that are included in the current response. These status codes are applicable to any response method.

The Server encountered an unexpected condition and could not complete the client's request. · 500.12 - The application is busy restarting on the Web server. · 500.13 - Web server too busy. · 500.15 -- Direct requests to Global.asa are not allowed. · 500.16 -- UNC authorization credentials are incorrect. This error code is specific to IIS 6.0. · 500.18 -- URL authorization store cannot be opened. This error code is specific to IIS 6.0. · 500.100 -- Internal ASP error. · 501-Not Implemented Server does Not support the functionality required to implement the request and header values specify unimplemented configurations. For example, a customer makes a PUT request that is not supported by the server. · 502-BAD Gateway When the server acts as a Gateway or proxy, it accesses the next server to complete the request, but the server returns an invalid reply. Also said that the Web server used as a gateway or proxy server received an invalid response. · 502.1 - CGI application times out. · 502.2 - CGI application error. · 503-service Unavailable The Service is Unavailable. The server does not respond due to maintenance or heavy load. For example, the Servlet might return 503 if the database connection pool is full. The server can provide a retry-after header when it returns 503. This error code is specific to IIS 6.0. · 504 - Gateway Timeout Gateway Timeout, used by the server acting as a proxy or Gateway, indicates that the remote server cannot receive a reply in time. (New in HTTP 1.1). · 505-HTTP Version Not Supported The server does Not support the HTTP Version specified in the request. (New in HTTP 1.1)Copy the code