http-delete

So, given that the DELETE verb in Http is idempotent, when I issue the following request, what should happen the second (or third, or fourth, etc...)? DELETE /person/123 The first time, the resource is deleted and I return a 204 (successful, no content). Should I return a 204 on subsequent calls or a 404 (not found)? As HTTP requests in a stateless system should be independent, the results of one request should not be dependent on a previous request. Consider what should happen if two users did a DELETE on the same resource simultaneously. It makes sense for the second request to get a 404.

I'm working on a project of RESTful web services, i'm using Apache Tomcat and JAX-RS. I want to accept DELETE requests from client but whenever i send a DELETE request from Advanced REST client Chrome plugin it gives response code 403 Forbidden. So how can i make Apche Tomcat accept DELETE request? Tomcat was blocking DELETE methods for me because of my CORS filters. I needed new filters registered in my web.xml file. Here's an example of a very permissive one: <filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> <init-param> <param

According to the "REST ideology" what should be in the response body for a PUT/POST/DELETE requests? What about return codes? Is HTTP_OK enough? What is the reason for such conventions, if any? I've found a good post describing POST/PUT differences: POST vs PUT But it still doesn't answer my question. Darrel Miller Forgive the flippancy, but if you are doing REST over HTTP then RFC7231 describes exactly what behaviour is expected from GET, PUT, POST and DELETE. Update (Jul 3 '14): The HTTP spec intentionally does not define what is returned from POST or DELETE. The spec only defines what needs

I'm trying to talk to a somewhat RESTful API from an Angular 2 frontend. To remove some item from a collection, I need to send some other data in addition to the removée unique id(that can be appended to the url), namely an authentication token, some collection info and some ancilliary data. The most straightforward way I've found to do so is putting the authentication token in the request Headers, and other data in the body. However, the Http module of Angular 2 doesn't quite approve of a DELETE request with a body, and trying to make this request let headers= new Headers(); headers.append(

Introduction I've read the following: Hypertext Transfer Protocol (HTTP) is the life of the web. It's used every time you transfer a document, or make an AJAX request. But HTTP is surprisingly a relative unknown among some web developers. The HTTP verbs comprise a major portion of our “uniform interface” constraint and provide us the action counterpart to the noun-based resource. The primary or most-commonly-used HTTP verbs (or methods, as they are properly called) are POST, GET, PUT , and DELETE . Huh? Well, we came to the point I lost track of things. PUT and DELETE , they say. I've only