I would go with 409: Conflict, because what you have is a violation of resource state. 405: Method Not Allowed would also work. If you’d want to use a 405, you’d have to send an Allow header to indicate the supported methods, and the supported methods would vary depeding on the resource’s state. In my … Read more
Have you tried overriding HttpEntityEnclosingRequestBase as follows: import org.apache.http.client.methods.HttpEntityEnclosingRequestBase; import java.net.URI; import org.apache.http.annotation.NotThreadSafe; @NotThreadSafe class HttpDeleteWithBody extends HttpEntityEnclosingRequestBase { public static final String METHOD_NAME = “DELETE”; public String getMethod() { return METHOD_NAME; } public HttpDeleteWithBody(final String uri) { super(); setURI(URI.create(uri)); } public HttpDeleteWithBody(final URI uri) { super(); setURI(uri); } public HttpDeleteWithBody() { super(); } } … Read more
Jon Skeet’s answer is the canonical answer. But: Suppose you have a link: href = “https://stackoverflow.com/questions/786070/\myApp\DeleteImportantData.aspx?UserID=27” and the google-bot comes along and indexes your page? What happens then?
Was trying to figure this out for a rails app that was using Angular on the front end; these seems to work for that environment: <a data-confirm=”Are you sure?” data-method=”delete” href=”https://stackoverflow.com/link-to-resource” rel=”nofollow”>Delete</a> Edit: Just to give everyone a heads up, I think you still need to have jQuery for this to work. I removed jQuery … Read more
Since you are in a bash environment, you could encode the hash OXYugGKg207g5uN/07V before passing it to curl. A straight-forward approach would be to use its byte representation %4f%58%59%75%67%47%4b%67%32%30%37%67%35%75%4e%2f%30%37%56 To get that, call: echo -ne “OXYugGKg207g5uN/07V” | xxd -plain | tr -d ‘\n’ | sed ‘s/\(..\)/%\1/g’ It will give you: %4f%58%59%75%67%47%4b%67%32%30%37%67%35%75%4e%2f%30%37%56 The complete one-liner including … Read more
Going by the book: RFC 2616-9.7: The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method MAY be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation has been carried out, even if the status code returned from … Read more
What are these methods (PUT) and (DELETE) for… There are a lot of words to spend to explain this, and I’m not skilled enough to do it, but as already posted, a quick recap of what the HTTP specification describes. The protocol basically says this: use GET when you need to access a resource and … Read more
Go to Handler Mappings in your IIS Manager. Find ExtensionlessUrlHandler-Integrated-4.0, double click it. Click Request Restrictions… button and on Verbs tab, add both DELETE and PUT. Possible WebDav Publisher issue You’ve mention on a deleted post you were running on a 2008 server right? Try removing webDav role, or disable it from your site config: … Read more
It is explicitly mentioned here in the RFC The short answer is: You should include a response body with an entity describing the deleted item/resource if you return 200. 202 is something like an asynchronous request/response return status. 204 says explicitly that you do not include a response body
Here is a fetch POST example. You can do the same for DELETE. function createNewProfile(profile) { const formData = new FormData(); formData.append(‘first_name’, profile.firstName); formData.append(‘last_name’, profile.lastName); formData.append(’email’, profile.email); return fetch(‘http://example.com/api/v1/registration’, { method: ‘POST’, body: formData }).then(response => response.json()) } createNewProfile(profile) .then((json) => { // handle success }) .catch(error => error);