Common Http/ftp/websocket error code Daquan-Go

HTTP1XX message

This type of status code, on behalf of which the request has been accepted, needs to be processed. This type of response is a temporary response that contains only the status line and some optional response header information and ends with a blank line. Because no 1XX status codes are defined in the HTTP/1.0 protocol, the server prohibits sending a 1xx response to such clients unless under some experimental conditions. These status codes represent a response that is informational and identifies other actions that the customer should take.

• 100-The client should continue to send the request

• 101-Switching Protocol

• 102-Processing will continue to execute

2XX success

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

• 200-(successful) The request was successful, and the desired response header or data body will be returned with this response.

• 201-(created) the request was successful and the server has created a new resource:

• 202-(accepted) the server has accepted the request, but it has not been processed.

• 203-(non-authoritative information) the server successfully processed the request, but returned information that might have come from another source.

• 204-(no content) the server successfully processed the request, but did not return any content.

• 205-(Reset content) the server successfully processed the request, but did not return any content.

• 206-(partial content) the server successfully processed a partial GET request.

3xx redirection

This type of status code represents the need for the client to take further action to complete the request. Typically, these status codes are used for redirection, and subsequent request addresses (redirected targets) are indicated in the location domain of the response. The browser should not automatically access more than 5 redirects, as recommended by the Http/1.0 Edition specification. Redirection is generally controlled by the browser to control the number of redirects, which can cause unnecessary resource consumption by the client

• 300-Multiple options, the requested resource has a range of feedback information to choose from.

• 301-permanently removed, the requested resource has been permanently moved to the new location.

• 302-temporary move, the requested resource is now temporarily responding to requests from different URIs.

• 303-View other locations, the response to the current request can be found on another URI, and the client should access that resource in a get way.

• 304-not modified. The requested webpage has not been modified since the last request. When the server returns this response, the Web page content is not returned.

• 305-Using a proxy, the requested resource must be accessed through the specified proxy.

• 306 -temporary redirection, in the latest version of the specification, the 306 status code is no longer in use.

• 307-Temporary redirection.

4XX Client Error

This type of status code indicates that the client may appear to have an error that prevents the server from processing.

• 400-Bad request.

• 401-access is denied.

• 402-Payment requirements.

• 403-Access Forbidden

  • 403.1-execution access is forbidden.

  • 403.2-Read access is forbidden.

  • 403.3-Write access is forbidden.

  • 403.4-Requires SSL.

  • 403.5-requires SSL 128. The

  • 403.6-ip address is rejected.

  • 403.7-Requires a client certificate.

  • 403.8-site access is denied.

  • 403.9-Too many users.

  • 403.10-the configuration is not valid.

  • 403.11-Password change.

  • 403.12-denies access to the mapping table.

  • 403.13-The client certificate is revoked.

  • 403.14-Deny directory list.

  • 403.15-Client access permission exceeded.

  • 403.16-client certificate is untrusted or invalid.

  • 403.17-The client certificate has expired or has not yet taken effect.

  • 403.18-The requested URL cannot be executed in the current application pool.

  • 403.19-CGI cannot be executed for clients in this application pool.

  • 403.20-passport Login failed.

• 404-not found.

  • 404.0-(None) – No files or directories found.

  • 404.1-Unable to access the WEB site on the requested port.

  • The 404.2-web service extension lockout policy blocks this request.

  • The 404.3-mime mapping policy blocks this request.

• 405-The HTTP verb used to access this page is not allowed (method not allowed)

• 406-The client browser does not accept the MIME type of the requested page.

• 407-proxy authentication is required.

• 408-the request timed out.

• 409-The request cannot be completed because there is a conflict between the current state of the requested resource and the request.

• 410-The requested resource is no longer available on the server, and there are no known forwarding addresses.

• 411-The server refuses to accept the request without defining a content-length header.

• 412-Precondition failed.

• 413– request entity is too large.

• 414-The request URI is too long.

• 415– media types not supported.

• The range requested by 416– is not sufficient.

• 417– execution failed.

• 418– This opcode is a traditional April Fools ' joke in 1998 as an IETF.

• 421– the number of connections from the current client's IP address to the server exceeds the maximum range of server licenses.

• The 422– request is well-formed, but cannot respond because of a semantic error.

• 423– the current resource is locked.

• 424– the current request failed due to an error that occurred in a previous request.

• 425– an unordered collection.

• The 426– client should switch to tls/1.0.

• 451– (newly added by IETF after 2015 approval) The visit was rejected as a result of legal requirements.

5XX Server Error

This type of status code indicates that the server has an error or an abnormal state in the process of processing the request, or that the server is aware that the processing of the request cannot be completed with the current hardware and software resources.

• 500-Internal server error.

• 501-not implemented, the header value specifies a configuration that is not implemented.

• 502-Error Gateway, the WEB server was used as a gateway or proxy server when an invalid response was received.

• 503-The service is not available, this error code is specific to IIS 6.0.

• 504-When the network timeout, the server as a gateway or proxy, did not receive the request from the upstream server in time.

• The 505-http version is not supported and the server does not support the HTTP protocol version used in the request.

• 506-The server is not configured correctly.

• 507-Insufficient storage space. The server cannot store the content necessary to complete the request. The situation is considered to be temporary.

• 509-bandwidth exceeds the limit. This is not an official status code, but is still widely used.

• 510-There is no extension, and the policy required to get the resource is not met.

FTP1XX Preliminary

A positive initial response, these status codes indicate that an operation has started successfully, but the client wants to get another reply before continuing with the new command.

• 110 Restart Tag reply.

• 120 service is ready, starting in nnn minutes.

• 125 The data connection is open and the transfer is starting.

• 150 file status OK, ready to open data connection.

2XX Complete

A positive completion of the reply, an operation has been completed successfully. The client can execute the new command.

• 200 command OK.

• 202 commands are not executed and there are too many commands on the site.

• 211 System Status, or system help reply.

• 212 Directory status.

• 213 file status.

• 214 Help message.

• 215 Name System type, where name is the formal system name listed in the Assigned Numbers document.

• 220 The service is ready to execute the request of the new user.

• 221 Service closes the control connection. If appropriate, please log out.

• 225 Data connection Open, no in-progress transfer.

• 226 Close the data connection. The requested file operation was successful (for example, transferring a file or discarding a file).

• 227 Enter passive mode (H1,H2,H3,H4,P1,P2).

• 230 The user is logged in and continues.

• 250 The requested file operation is correct and completed.

• 257 "PATHNAME" has been created.

3xx Middle

A positive intermediate response, the command was successful, but the server needed more information from the client to complete the processing of the request.

• 331 user name is correct, password required.

• 332 You need to log in to your account.

• 350 The requested file operation is waiting for further information.

4xx transient negation

Transient negation completes the reply, the command is unsuccessful, but the error is temporary. If the client retries the command, it may execute successfully.

• 421 service is not available and the control connection is shutting down. If the service determines that it must be closed, this response is sent to any command.

• 425 The data connection cannot be opened.

• 426 Connection closed; Transfer aborted.

• 450 The requested file operation was not performed. The file is not available (for example, the file is busy).

• 451 requested operation aborted: Local error is being processed.

• 452 the requested operation was not performed. The system does not have enough storage space.

5xx Permanent Negation

A permanent negation completes the reply, the command is unsuccessful, and the error is permanent. If the client retries the command, the same error will occur again.

• 500 syntax error, command not recognized. This may include errors such as the command line being too long.

• 501 There are syntax errors in the arguments.

• 502 command not executed.

• 503 wrong sequence of commands.

• 504 command not executed for this parameter.

• 530 not logged in.

• 532 The account is required to store the file.

• 550 the requested operation was not performed. The file is not available (for example, the file was not found and no access was granted).

• 551 requested operation aborted: unknown page type.

• 552 requested file operation terminated abnormally: storage allocation exceeded (for current directory or dataset).

• 553 The requested operation was not performed. The file name is not allowed.

6XX protected

• Series,replies regarding confidentiality and integrity

• 631 Integrity protected reply.

• 632 Confidentiality and integrity protected reply.

• 633 confidentiality protected reply.

WebSockets Status Code

WebSockets Closeevent will be sent to clients using WebSockets when the connection is closed. It is used in the OnClose event listener of the WebSocket object. The shutdown code sent by the server, the following is the assigned status code.

Status Code	name	Description
0–999	-	Reserved segment, not used.
1000	Close_normal	normal shutdown; The link has successfully completed the task, regardless of why it was created.
1001	Close_going_away	The terminal leaves, possibly due to server error, or because the browser is jumping from the page that opened the connection.
1002	Close_protocol_error	The connection was interrupted because of a protocol error.
1003	close_unsupported	The connection was disconnected due to an disallowed data type (for example, a terminal receiving only text data received binary data).
1004	-	Keep. Its meaning may be defined in the future.
1005	Close_no_status	Keep. Indicates that no expected status code was received.
1006	Close_abnormal	Keep. Used to expect to receive a status code when the connection is not properly closed (that is, no closed frames are sent).
1007	Unsupported Data	Disconnected (such as non-UTF-8 data contained in a text message) due to a malformed data.
1008	Policy violation	The connection was dropped because it received data that did not conform to the contract. This is a generic status code for scenarios that are not suitable for use with 1003 and 1009 status codes.
1009	Close_too_large	The connection was dropped because of a large data frame being received.
1010	Missing Extension	The client expects the server to agree on one or more extensions, but the server is not processing, so the client disconnects.
1011	Internal Error	The client disconnects from the server because it encountered unexpected conditions that prevented it from completing the request.
1012	Service Restart	The server was disconnected because of a reboot. [Ref]
1013	Try Again Later	The server disconnects from a portion of the client connection due to temporary reasons such as server overloading. [Ref]
1014	-	by WebSocket	Standard reserved for future use.
1015	TLS handshake	Keep. Indicates that the connection was closed because the TLS handshake could not be completed (for example, the server certificate could not be verified).
1016–1999	-	Reserved for future use by the WebSocket standard.
2000–2999	-	Reserved for use by WebSocket expansion.
3000–3999	-	Can be used by a library or framework. Should not be used by the app. can be registered on the IANA, on a first-come-first-served basis.
4000–4999	-	Can be used by an app.

Resources

• HTTP Status Code list

• FTP Status Code list

• MDN closeevent

• HTTP 404

• List of FTP server return codes

• HTTP Overview

• Help for HTTP Error 403: "Forbidden"

Common Http/ftp/websocket error code Daquan-Go