Error Message 202
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
Http 202
are no required headers for this class of status code. Since HTTP/1.0 did http code 302 not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under
Http 403
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. http 404 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 not forward the corresponding 100 (Continue) http status codes cheat sheet 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 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 th
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e This is a list
Http Response Example
of Hypertext Transfer Protocol (HTTP) response status codes. It includes codes from http 422 IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. The first digit of the status
Http 500
code specifies one of five classes of response; an HTTP client must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human-readable alternative can https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information,[3] but not all of those are here (note that these sub-codes only appear in the response payload and in documentation; not in https://en.wikipedia.org/wiki/List_of_HTTP_status_codes the place of an actual HTTP status code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 5xx Server Error 6 Unofficial codes 6.1 Internet Information Services 6.2 nginx 6.3 Cloudflare 7 See also 8 Notes 9 References 10 External links 1xx Informational[edit] 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[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll https://msdn.microsoft.com/en-us/library/aa976528(v=vs.71).aspx be auto redirected in 1 second. Reference Error Messages Error Messages A-Z Error Messages A-Z Invalid path or file name (Error 202) Invalid path or file name (Error 202) Invalid path or file name (Error 202) "cursor" must be http://www.clickatell.com/developers/api-docs/error-code-202/ created with SELECT ... INTO TABLE (Error 1815) "field | variable" is not unique and must be qualified (Error 1832) "field" is not related to the current work area (Error 1165) "field" phrase is not found (Error 1130) error message "file" is not a Visual FoxPro .EXE file (Error 1196) "file" is not an object file (Error 1309) "name" band is too large to fit on page (Error 1298) "name" can only be used within a method (Error 1929) "name" cannot be closed while suspended (Error 1932) "name" cannot be enumerated (Error 1794) "name" internal consistency error (Error 1462) "name" is a method, event, or object (Error 1737) "name" is a read-only property (Error 1740) "name" is error message 202 not a file variable (Error 226) "name" is not a function, procedure or program (Error 1992) "name" is not a valid resource file (Error 1294) "name" is not a variable (Error 225) "name" is not a Visual FoxPro event (Error 1745) "name" is not an array (Error 232) "name" is not an object (Error 1924) "name" objects cannot return a value (Error 1983) "OLE error" (Error 1429) ** or ^ domain error (Error 78) *bad date* *Interrupted* .DBC internal consistency error (Error 1550) .DIF file header is invalid (Error 115) .DIF type indicator is invalid (Error 117) .DIF vector is invalid - .DBF field mismatch (Error 116) .SYLK file dimension bounds are invalid (Error 120) .SYLK file format is invalid (Error 121) .SYLK file header is invalid (Error 119) A .DBF-style Help file is required (Error 1727) A Key cannot be specified when adding an item to this collection. (Error 2064) A Key must be specified when adding an item to this collection. (Error 2063) A member object with this name already exists (Error 1771) A sharing violation occurred. (Error 2024) A stored procedure is executing (Error 1538) A subdirectory or file "name" already exists (Error 1961) A table in multiple relationships can only have one child order (Error 1889) Access to system Registry denied (Error 1640) ADODB.Command is already opened. (Error 2081) ADODB.Recordset is already opened. (Error 2080) ADODB.Records
SMS APIs Scripts SMS gateway API documentation SMS Gateway live test Tutorials Resources Use cases White papers Case studies Videos Blog Blog home Products & services Industry insights Solutions Community Help Frequently asked questions Contact sales Contact MTS Contact support Create your free account Log in REST Overview of the REST API features Using the REST API Send message Message status Retrieve balance Stop message Get coverage Response status codes Error codes CLICKATELL SECURE Request Secure GridPlus authentication Using the Secure REST API Request Secure Pin authentication Verify Secure Pin 2FA request Request Secure Grid authentication Verify Secure Grid 2FA request Request image categories for GridPlus Verify Secure GridPlus authentication request Secure REST API response status codes HTTP Overview of the HTTP API features Using the HTTP API Send message Message status Retrieve account balance Get coverage Stop messages Authentication Ping Error codes SMTP Overview of the SMTP API features Using the SMTP API Send basic message Template based messaging Text vs data parameter Error codes FTP Overview of the FTP API features Using the FTP API Login credentials Send basic message Tracking a message Send templated bulk message Error codes SOAP Overview of the SOAP API features Using the SOAP API Send message Message status Retrieve balance Get coverage Stop message Authentication Ping Error codes SMPP Using the SMPP API Connection Details Supported PDUs Unsupported PDUs PDU Details Standard Optional Parameters (TLVs) Vendor-specific Optional Parameters (TLVs) TWO-WAY MESSAGING INFORMATION Message status codes Test number range Glossary ADVANCED MESSAGE SEND Parameter overview Binary Set your own message ID Concatenation Message prioritization (queuing) Message validity Callback (push status