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
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);
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. The same should be true if … Read more
This is fairly common and there is even a somewhat standard http header for it. It’s called “http method override” and you’ll find some good stuff in this question X-HTTP-Method-Override gives NotFound (404) on ASP.NET Web API
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?
To perform an HTTP PUT: URL url = new URL(“http://www.example.com/resource”); HttpURLConnection httpCon = (HttpURLConnection) url.openConnection(); httpCon.setDoOutput(true); httpCon.setRequestMethod(“PUT”); OutputStreamWriter out = new OutputStreamWriter( httpCon.getOutputStream()); out.write(“Resource content”); out.close(); httpCon.getInputStream(); To perform an HTTP DELETE: URL url = new URL(“http://www.example.com/resource”); HttpURLConnection httpCon = (HttpURLConnection) url.openConnection(); httpCon.setDoOutput(true); httpCon.setRequestProperty( “Content-Type”, “application/x-www-form-urlencoded” ); httpCon.setRequestMethod(“DELETE”); httpCon.connect();
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. EDIT: 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 … Read more