Http Error Codes Wikipedia
Contents |
consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required http status codes cheat sheet headers for this class of status code. Since HTTP/1.0 did not define
Http Response Example
any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental
Http Error Wordpress
conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status
Http 422
message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and 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 http code 403 not forward the corresponding 100 (Continue) response(s).) Wikipedia Request received, continuing process. 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. Since HTTP/1.0 did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions. 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 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. Wikipedia This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which
Successful3xx - Redirection4xx - Client Error5xx - Server Error HTTP Status Codes Last modified 22:51, 22 May 2012 Table of contents1xx - Informational2xx - Successful3xx - Redirection4xx - Client Error5xx - Server Error http code 302 Each Status-Code is described below, including a description of which method(s) it can follow http 504 and any metainformation required in the response. 1xx - Informational This class of status code indicates a provisional response, consisting only of http 503 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 did not define any 1xx status codes, servers MUST NOT send http://www.restapitutorial.com/httpstatuscodes.html a 1xx response to 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 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 its client has been closed, or unless the http://www.restpatterns.org/HTTP_Status_Codes 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).) 100 - Continue101 - Switching Protocols 2xx - Successful This class of status code indicates that the client's request was successfully received, understood, and accepted. 200 - OK201 - Created202 - Accepted203 - Non-Authoritative Information204 - No Content205 - Reset Content206 - Partial Content207 - Multi-Status 3xx - Redirection This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection. Note: previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that there might be clients that implement such a fixed limitation. 300 - Multiple Choices301 - Moved Permanently302 - Found303 - See Other304 - Not Modified305 - Use Proxy306 - (Reserved)307 - Temporary Redirect 4xx - Client Error The 4xx class of status c
Spelling Like Pages Local Site Map ------------------------ Rename Page Copy Page Delete Page ------------------------ My Pages Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow Here http://wiki.apache.org/httpd/CommonHTTPStatusCodes is a list of most of the used http status codes with an explanation of what they mean. Code Message Description See also 1xx - Informational 100 Continue https://wiki.guildwars2.com/wiki/Error_code Allows the client to determine if the origin server is willing to accept the request, for example based on the request headers, before the client sends the http error request body. If the request is not accepted, the status code 406 is returned. Example usage: http client checks if chunked transfer encoding is allowed before sending the full request body. 101 Switching Protocols Response from the httpd when an upgrade header is received and the requested protocol is supported by the httpd. Will http error codes be followed by a Upgrade header specifying the tokens of the protocol stack it is switching to. Example usage: http client wants to switch from HTTP/1.1 to TLS/1.0 in order to set up a secure communication channel. 102 Processing Part of the http status code extensions for Distributed Authoring (WebDAV). Should be sent to the http client when a request takes a long period to complete. Will always be followed by the final response indicating either success or failure of the request. This status code can be used to avoid connection timeouts preventing the response from being succesfully sent to the http client. RFC 2518 Section 10 2xx - Successful 200 OK Request has succeeded, content delivered normally. 201 Created Request has succeeded and has resulted in a new resource being created. Usually details on the resource such as its new URI and ETag information are included in the httpd response. Example usage: a POST request to a remote script that generat
sell 4:1019:0:0:101 10:4:5:3748:101 42:0:9001:3858:101 42:4:11:154:101 42:4:11:303:101 42:5:13:210:101 45:1000:7006:529:101 Unable to complete operation. Please try again in a few minutes. Common when servers are experiencing high volumes, causing connectivity issues. 4:1004:2:2791:101 4:1008:2:299 10:1005:2:1172 19:9:18:1607:101 19:9:19:1951:101 19:9:19:1786:101 19:9:19:1789:101 42:0:9001:3916:101 42:0:9001:3927 42:0:9001:3927:101 42:0:9001:3928 42:0:9001:3968 42:0:9001:4105 42:0:9001:4126 42:0:9001:4395 42:0:9001:4418 42:0:9001:4419 42:4:7:578 42:4:7:602 42:4:11:143:101 42:4:18:516:101 42:5:7:1008:101 42:5:13:210:101 42:5:13:318:101 42:6:3:2060 42:6:3:2158 42:6:3:2242 42:1000:7006:852 42:1000:7006:854 42:1000:7006:888 42:1000:7006:888:101 42:1000:7006:891:101 42:1000:7006:1219 42:1000:7006:1327:101 42:1000:7006:1230 42:1000:7006:1339 42:1000:9001:4105:101 42:1000:9001:4119:101 42:1030:7:208 The game client is unable to gain access to the log-in server at this time. This is most commonly caused by a firewall or router settings, security applications, or connecting through a campus network. For additional support, please visit http://support.guildwars2.com. Also appears when there are server problems on ArenaNet's side, such as too much traffic. The codes starting with 19 seem to be related to the sPvP servers 5:11:3:157:101 5:11:3:159:101 Network issue. Failing to get connected to Guild Wars 2 may be caused by the routeur or by a network server failure. If the problem remains, please contact the online assistance. 7:0:0:793:101 7:11:1:502 7:11:3:189:101 7:11:3:191:101 7:1000:7006:383 7:1000:7006:653:101 7:1000:7006:771:101 The game client lost its connection to the server. Please wait a few minutes before restarting the client and trying again. 9:4:5:1067:101 9:4:5:1093:101 Your account is all prepared, but there is no Beta event running right now. Please come back and join us at the start of the next Beta event. For more information, visit the Guild Wars 2 website. The 1093 variant might appear if: You used a pre-order serial code, instead of a pre-purchase code; only the latter guarantees access to Beta Weekend Events. You used an unauthorized code. 9:4:5:1148:101 9:4:5:1162 9:4:5:1184:101 9:4:5:1186 Either there is no Guild Wars 2 event or this account is not authorized to participate in one. If you believe an event is running that you should have a