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
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
You can add a handler to deal with this type of request. Create a class derive from “DelegatingHandler”: public class PreflightRequestsHandler : DelegatingHandler { protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) { if (request.Headers.Contains(“Origin”) && request.Method.Method.Equals(“OPTIONS”)) { var response = new HttpResponseMessage { StatusCode = HttpStatusCode.OK }; // Define and add values to variables: origins, … Read more
The http.delete(url, options) does accept a body. You just need to put it within the options object. http.delete(‘/api/something’, new RequestOptions({ headers: headers, body: anyObject })) Reference options interface: https://angular.io/api/http/RequestOptions UPDATE: The above snippet only works for Angular 2.x, 4.x and 5.x. For versions 6.x onwards, Angular offers 15 different overloads. Check all overloads here: https://angular.io/api/common/http/HttpClient#delete … Read more
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 to be defined. The rest is … 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);
So after a number of tries, I found it working. Please follow the order sequence it’s very important else it won’t work axios.delete(URL, { headers: { Authorization: authorizationToken }, data: { source: source } });
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?