Http Error Status 200
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
Http Response Example
headers for this class of status code. Since HTTP/1.0 did not define any http code 302 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client http status codes cheat sheet 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
Http Error Wordpress
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) response(s).) 10.1.1 100 Continue The client SHOULD continue
Http 422
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 that use such features. 10.2 Successful 2xx This class of status code indicates that the client's re
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 http 404 is the object returned by the request. It is a MIME format object.
Http 403
It is in MIME format, and may only be in text/plain, text/html or one fo the formats specified as acceptable http 502 in the request. OK 200 The request 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 https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html newly created document should be known. Accepted 202 The request has 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 https://www.w3.org/Protocols/HTTP/HTRESP.html command, this indicates that the returned metainformation is not a definitive set of the object from 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://stackoverflow.com/questions/27921537/returning-http-200-ok-with-error-within-response-body more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community http://100pulse.com/http-statuscode/200.jsp Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Returning http 200 OK with error within response body up http error vote 3 down vote favorite 3 I'm wondering if it is correct to return HTTP 200 OK when error on server side occurred with some error inside of response body. Example: We're sending http GET Something unexpected happened on the server side. Server returns http 200 OK status code with error inside a response (e.g. {"status":"some error occured"} Is is correct behavior or not? Shouldn't we change status http error status code? http http-status-code-400 http-status-code-200 share|improve this question edited Jan 14 '15 at 10:01 CodeCaster 76.9k983136 asked Jan 13 '15 at 11:53 krzakov 3053923 1 HTTP 200 means transmission is OK on the http level. This has nothing to do with success or failure of your "business code". In this case the HTTP 200 indicates that your "business code error message" was succesfully transferred ;-) Alternatively you could let your server respond with HTTP 500 meaning "internal error". This is more typical for technical or unrecoverable problems on the server. –geert3 Jan 13 '15 at 11:57 Can anybody confirm that? I talked with some programmers and I can hear different opinions. –krzakov Jan 13 '15 at 12:01 add a comment| 3 Answers 3 active oldest votes up vote 10 down vote No, this is very incorrect. HTTP is an application protocol. 200 implies that the response contains a payload that represents the status of the requested resource. An error message usually is not a representation of that resource. If something goes wrong while processing GET, the right status code is 4xx ("you messed up") or 5xx ("I messed up"). share|improve this answer answered Jan 13 '15 at 13:05 Julian R
by far the most common returned. It means, simply, that the request was received and understood and is being processed. Why it Occurs Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action. What it Means The request has succeeded. The information returned with the response is dependent on the method used in the request. 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 02:18:28 GMT All Rights reserved © 100pulse.com Terms | Privacy | Sitemap