Http Error Number
Contents |
response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 http response example did not define any 1xx status codes, servers MUST NOT send a 1xx response to
Http Status Codes Cheat Sheet
an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a http code 302 regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and
Http Error Wordpress
its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) 10.1.1 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been http code 403 rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. 10.1.2 101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features. 10.2 Successful 2xx This class of status code indicates that the client's request was successfully received, understood, and accepted. 10.2.1 200 OK The request has succeeded. The information returned with the response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response; HEAD the entity-header fields corresponding to the requested resource are sent in
sections of messages Error, Forward and redirection responses may be used to contain human-readable diagnostic information. Success 2xx These codes indicate success. The body section if present is the object returned by
Http 422
the request. It is a MIME format object. It is in MIME format, and
Http 404
may only be in text/plain, text/html or one fo the formats specified as acceptable in the request. OK 200 The request http 502 was fulfilled. CREATED 201 Following a POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be known. Accepted 202 The request has https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html been accepted for processing, but the processing has not been completed. The request may or may not eventually be acted upon, as it may be disallowed when processing actually takes place. there is no facility for status returns from asynchronous operations such as this. Partial Information 203 When received in the response to a GET command, this indicates that the returned metainformation is not a definitive set of the object from https://www.w3.org/Protocols/HTTP/HTRESP.html a server with a copy of the object, but is from a private overlaid web. This may include annotation information about the object, for example. No Response 204 Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time. Error 4xx, 5xx The 4xx codes are intended for cases in which the client seems to have erred, and the 5xx codes for the cases in which the server is aware that the server has erred. It is impossible to distinguish these cases in general, so the difference is only informational. The body section may contain a document describing the error in human readable form. The document is in MIME format, and may only be in text/plain, text/html or one for the formats specified as acceptable in the request. Bad request 400 The request had bad syntax or was inherently impossible to be satisfied. Unauthorized 401 The parameter to this message gives a specification of authorization schemes which are acceptable. The client should retry the request with a suitable Authorization header. PaymentRequired 402 The parameter to this message gives a specification of charging s
» HTTP Status and Error Codes HTTP Status and Error Codes 3 Years Ago GlobalSCAPE 5 CuteFTP for Windows THE INFORMATION IN THIS ARTICLE APPLIES TO: All GlobalSCAPE products, all versions Refer to https://kb.globalscape.com/KnowledgebaseArticle11144.aspx for EFT-specific https://kb.globalscape.com/KnowledgebaseArticle10141.aspx HTTP error codes DISCUSSION During your HTTP sessions, you'll receive various numbered codes from Web servers. When connected via HTTP, CuteFTP and HTTP servers to which you connect can display https://docs.angularjs.org/api/ng/service/$http these codes in the log window. Some codes represent errors. Most others simply communicate the status of the connection. Here are brief explanations for the most common status and error http error codes. The list below are standard HTTP codes. Numbers outside this list are proprietary to the Server or Client that you are using. Error or Status Code Description 100 Series Informational - These status codes indicate a provisional response. The client should be prepared to receive one or more 1xx responses before receiving a regular response. 100 Continue. 101 Switching protocols. http error number 200 Series Success - This class of status codes indicates that the server successfully accepted the client request. 200 The client request has succeeded. This status code indicates that the Web server has successfully processed the request. 201 Created. 202 Accepted. 203 Non-authoritative information. 204 No content. 205 Reset content. 206 Partial content. 300 Series Redirection - The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server or repeat the request by using a proxy server. 302 Object moved. 304 Not modified. The client requests a document that is already in its cache and the document has not been modified since it was cached. The client uses the cached copy of the document, instead of downloading it from the server 307 Temporary redirect. 400 Series Client Error - An error occurs, and the client appears to be at fault. For example, the client may request a page that does not exist, or the client may not provide valid authentication information. 400 Bad request. 401 Access denied.
{{ key }} {{ item.name }} Close / {{crumb.name}} Show / Hide Table of Contents {{ navGroup.name }} {{navItem.extra.text}} {{navItem.name}} Close Loading... Back to top Super-powered by Google ©2010-2016 ( ) Code licensed under The MIT License. Documentation licensed under CC BY 3.0.