Ok 200 Error
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. status code 200 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 an HTTP/1.0 client except
Http Code 302
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)
Http 404
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 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 http status codes cheat sheet 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 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
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 more about Stack Overflow the company Business Learn http 403 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags http 422 Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, http 502 helping each other. Join them; it only takes a minute: Sign up Returning http 200 OK with error within response body up vote 3 down vote favorite 3 I'm wondering if it is correct to return HTTP https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 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 code? http http-status-code-400 http-status-code-200 share|improve this question edited Jan 14 '15 at 10:01 CodeCaster 77.2k984137 asked Jan 13 '15 at 11:53 krzakov 3103923 http://stackoverflow.com/questions/27921537/returning-http-200-ok-with-error-within-response-body 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 Reschke 19.9k43853 So basically You agree with previous answer? –krzakov Jan 13 '15 at 14:44 1 No, I disagree completely with the first part that claims that it would be ok to return 200. –Julian Reschke Jan 13 '15 at 15:02 I'm totall
by far the http://ckeditor.com/forums/Support/XML-request-error-OK-200-0 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 status code 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 ok 200 error 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 : 22-Oct-2016 11:04:22 GMT All Rights reserved © 100pulse.com Terms | Privacy | Sitemap
newsletter I found a bug Documentation Fork us on GitHub Search Search in whole site Search Type here and hit enter... RSS Log In / Sign Up Log in Username * Your user name Password * Password Log in using social networks Facebook Twitter Yahoo Sign up CKEditor About About Features for you Who is using License Additional products Demo Add-ons Plugins Skins Submit plugin Submit skin Get involved Get involved Newsletter sign-up Blog Support Support FAQ Documentation CKEditor SDK Download Add new post Home›Forums›CKFinder›Support Newsletter sign-up Twitter Facebook G+ The forum operates in read-only mode. Please head to StackOverflow for support. Last post Sun, 11/02/2008 - 22:20 #1 eruna Joined: 09/04/2008 Posts: 22 XML request error: OK (200) Hi,I've been getting this error on the CKfinder on the test standalone page:URL requested: "http://bflybuzz.com/modules/ckfinder/core/connector/php/connector.php?command=Init"Server response:Status: 200Response text:Any ideas?TY Top Wed, 11/05/2008 - 04:21 #2 eruna Joined: 09/04/2008 Posts: 22 Re: XML request error: OK (200) I figured out the problem. Some files were missing. I reupoaded the module and it worked. Top Fri, 01/30/2009 - 16:35 #3 rian Joined: 31/08/2007 Posts: 15 Re: XML request error: OK (200) Hi, I'm having the same problem but only in IE and only on certain computers, in Firefox it works ok, with the same computers... Any idea's? Something with the security settings of IE? Top Mon, 02/02/2009 - 10:30 #4 rian Joined: 31/08/2007 Posts: 15 Re: XML request error: OK (200) Hi, I found the solution to the XML error message: When someone uploads a file with in the name other characters than ascii characters e.g. with an umlaut, the message occurs. OK, took me a while, but this is an error between keyboard and chair; now i'm going to shoot my CMS users. Top Tue, 02/03/2009 - 11:22 #5 wiktor Joined: 16/07/2007 Posts: 1669 Re: XML request error: OK (200) @rian - seems to be a bug, I have a couple of questions..Which version of CKFinder are you using (PHP,