Http 203 Error Code
Contents |
203 status code means that the request http status code 400 was received and understood, and that information sent
Http Code 403
back about the response is from a third party, rather than the original server. http status codes cheat sheet This is virtually identical in meaning to a 200 status code. Why it Occurs The returned metainformation in the entity-header is http code 302 not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result
Http Response Example
in a superset of the metainformation known by the origin server. What it Means This code may be used in place of 200 when the sender has a reason to believe that the information in the response's entity headers is different from what the origin server would send. Features Website Monitoring Monitor DNS Server Mail Server Monitoring Mysql Server Monitoring FTP Monitoring Port Monitoring Alerts & Reports Instant Notification Web Server Monitoring Report Public Report Template Free Uptime Button Monitoring Tools Webpage Availability Checker Port checker DNS Checker IP Finder Server location Finder and more... Reseller Affiliate Program Pricing Latest Updates Feedback Write a testimonial About Us Contact Us Follow Us on Twitter Facebook Server Time : 18-Oct-2016 01:01:00 GMT All Rights reserved © 100pulse.com Terms | Privacy | Sitemap
status code allows the http 404 proxy to notify recipients when a transformation has been
Http 502
applied, since that knowledge might impact later decisions regarding the content. For example, future cache http://100pulse.com/http-statuscode/203.jsp validation requests for the content might only be applicable along the same request path (through the same proxies). The 203 response is similar to the Warning code of 214 Transformation Applied2, https://httpstatuses.com/203 which has the advantage of being applicable to responses with any status code. A 203 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls3. 1 Transformations RFC7230 Section 5.7.2 2 Warning RFC7234 Section 5.5 3 Calculating Heuristic Freshness RFC7234 Section 4.2.2 Source: RFC7231 Section 6.3.4 203 Code References Rails HTTP Status Symbol :non_authoritative_information Go HTTP Status Constant http.StatusNonAuthoritativeInfo Symfony HTTP Status Constant Response::HTTP_NON_AUTHORITATIVE_INFORMATION Python2 HTTP Status Constant httplib.NON_AUTHORITATIVE_INFORMATION Python3+ HTTP Status Constant http.client.NON_AUTHORITATIVE_INFORMATION Python3.5+ HTTP Status Constant http.HTTPStatus.NON_AUTHORITATIVE_INFORMATION← Return to httpstatuses.com
& Guides Learn the Web Tutorials References Developer Guides Accessibility Game development ...more docs Mozilla Docs Add-ons Firefox WebExtensions Developer ToolsFeedback Get Firefox help Get web development help Join the https://developer.mozilla.org/en-US/docs/Web/HTTP/Status MDN community Report a content problem Report a bug Search Search Languages 日本語 (ja) 한국어 (ko) Русский (ru) 中文 (简体) (zh-CN) 正體中文 (繁體) (zh-TW) Add a translation Edit Advanced Advanced History Print https://kb.globalscape.com/KnowledgebaseArticle10141.aspx this article MDN Web technology For developers HTTP HTTP response status codes Your Search Results fscholz sivasain arulnithi rctgamer3 groovecoder dovgart Sheppy fusionchess HTTP response status codes In This Article Information responsesSuccessful responsesRedirection messagesClient http status error responsesServer error responses HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes: informational responses, successful responses, redirects, client errors, and servers errors. Information responses 100 Continue This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished. 101 Switching Protocol http status code This code is sent in response to an Upgrade: request header by the client, and indicates that the protocol the server is switching too. It was introduced to allow migration to an incompatible protocol version, and is not in common use. Successful responses 200 OK The request has succeeded. The meaning of a success varies depending on the HTTP method: GET: The resource has been fetched and is transmitted in the message body. HEAD: The entity headers are in the message body. POST: The resource describing the result of the action is transmitted in the message body. TRACE: The message body contains the request message as received by the server 201 Created The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request. 202 Accepted The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing. 203 Non-Authoritative Information This response code means returned meta-information set
» 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 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 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 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. 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. 401.1 Logon failed. The logon attempt is unsuccessful, probably because of a user name or password that is no