If you are using Spring, you have this enum org.springframework.web.bind.annotation.RequestMethod public enum RequestMethod { GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE; } EDIT : Here is the complete list of constants values in Java 6 You can see that some of those are available in the class HttpMethod but it contains less values than … Read more
There is an HTTP PURGE method, though it is not defined in the HTTP RFCs (which do allow for custom methods beyond the standard defined methods). Some HTTP servers and caching systems actually do implement PURGE, for instance Squid and Varnish: Squid: How can I purge an object from my cache? Varnish: Purging and banning … Read more
Here’s a solution with the rack-cors gem, which you said you tried. As others have mentioned, you didn’t give much detail in regards to which front-end framework you’re using and what the actual request looks like. So the following may not apply to you, but I hope it helps someone. In my case, the gem … Read more
Because the HTTP GET method is specified as idempotent, a GET request, by specification, can be resubmitted with the assumption that it will not change anything on the server. This is not the case for a HTTP POST which by specification can change the status of the application running on the server. So, by specification, … Read more
Here is the summary from RFC 7231, an updated version of the link @Darrel posted: HEAD – No defined body semantics. GET – No defined body semantics. PUT – Body supported. POST – Body supported. DELETE – No defined body semantics. TRACE – Body not supported. OPTIONS – Body supported but no semantics on usage … Read more
Despite some recommendations not to use the message body for DELETE requests, this approach may be appropriate in certain use cases. This is the approach we ended up using after evaluating the other options mentioned in the question/answers, and after collaborating with consumers of the service. While the use of the message body is not … Read more
If your login request is via a user supplying a username and password then a POST is preferable, as details will be sent in the HTTP messages body rather than the URL. Although it will still be sent plain text, unless you’re encrypting via https. The HTTP DELETE method is a request to delete something … Read more
Create = PUT with a new URI POST to a base URI returning a newly created URI Read = GET Update = PUT with an existing URI Delete = DELETE PUT can map to both Create and Update depending on the existence of the URI used with the PUT. POST maps to Create. Correction: POST … Read more
By default you use curl without explicitly saying which request method to use. If you just pass in a HTTP URL like curl http://example.com it will use GET. If you use -d or -F curl will use POST, -I will cause a HEAD and -T will make it a PUT. If for whatever reason you’re … Read more