Http Error 207
Contents |
207 - Multi-Status Last modified 22:01, 27 Oct 2008 Table of contentsNo headers The 207 (Multi-Status) status code provides status for multiple http code 403 independent operations (see Section13 for more information). A Multi-Status response conveys information http 207 example about multiple resources in situations where multiple status codes might be appropriate. The default Multi-Status response body is a
Http Code 302
text/xml or application/xml HTTP entity with a 'multistatus' root element. Further elements contain 200, 300, 400, and 500 series status codes generated during the method invocation. 100 series status codes SHOULD
Http 504
NOT be recorded in a 'response' XML element. Although '207' is used as the overall response status code, the recipient needs to consult the contents of the multistatus response body for further information about the success or failure of the method execution. The response MAY be used in success, partial success and also in failure situations. The 'multistatus' root element holds zero http 503 or more 'response' elements in any order, each with information about an individual resource. Each 'response' element MUST have an 'href' element to identify the resource. A Multi-Status response uses one out of two distinct formats for representing the status: A 'status' element as child of the 'response' element indicates the status of the message execution for the identified resource as a whole (for instance, see Section9.6.2). Some method definitions provide information about specific status codes clients should be prepared to see in a response. However, clients MUST be able to handle other status codes, using the generic rules defined in Section 10 of [RFC2616]. For PROPFIND and PROPPATCH, the format has been extended using the 'propstat' element instead of 'status', providing information about individual properties of a resource. This format is specific to PROPFIND and PROPPATCH, and is described in detail in Sections 9.1 and 9.2. Page statistics 13602 view(s) and 2 edit(s) Social share Share this page? Tags RFC4918 This page has no classifications. Comments You must sign in to post a comment. Attachments Powered by MindTouch TemplatesPopular
that follows is an XML http error 500 wordpress message and can contain a number of separate response codes, depending on how many sub-requests http://www.restpatterns.org/HTTP_Status_Codes/207_-_Multi-Status were made. What it Means This is a type of http error and if you monitor your website through 100 pulse, we will intimate you through mail or short message http://100pulse.com/http-statuscode/207.jsp service whenever you encounter 207 status code. 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 18:24:47 GMT All Rights reserved © 100pulse.com Terms | Privacy | Sitemap
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 http://stackoverflow.com/questions/30571489/what-are-applicable-scenarios-in-using-http-status-207-in-rest-api this site About Us Learn 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 Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign http error up What are applicable scenarios in using HTTP status 207 in REST API? up vote 4 down vote favorite Planning to use http status 207/ multi status as a response for updating/deleting list of objects in a REST api. I plan to respond with 204 if all succeeds and 207 if it's a mixture of successes/failures. Is this the right usage for 207? http error 207 What scenarios does http 207 commonly used on? web-services rest share|improve this question asked Jun 1 '15 at 10:45 froi 7741921 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted If you perform a destructive operation like POST, PUT, DELETE against more than one resource and the operations against each individual resource did not share a common outcome then you can go for 207. For example, If you DELETEd two resources and both were deleted you can expect If both DELETEs were forbidden, you'd expect 403. If one DELETE was successful but one was forbidden, you would receive 207. Some more discussion on 207 status. share|improve this answer answered Jun 1 '15 at 11:28 Sunil Kumar 8301720 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for?