Overview[1]#

HTTP Method (sometimes referred to as verb) to indicate the desired action to be performed on the identified resource.

What this resource represents, whether pre-existing data or data that is generated dynamically, depends on the implementation of the Service Provider.

Often, the resource corresponds to a file or the output of an executable residing on the server.

The HTTP/1.0 specification[11] defines the

• HTTP GET
• HTTP POST
• HTTP HEAD

HTTP Method

The HTTP/1.1 specification[12] added 5 new methods:

• HTTP OPTIONS
• HTTP PUT
• HTTP DELETE
• HTTP TRACE
• HTTP CONNECT

By being specified in these documents their semantics are well known and can be depended on. Any client can use any method and the server can be configured to support any combination of methods.

If a method is unknown to an intermediate it will be treated as an unsafe and non-idempotent method. There is no limit to the number of methods that can be defined and this allows for future methods to be specified without breaking existing infrastructure. For example, WebDAV defined 7 new methods and RFC 5789 specified the HTTP PATCH method.

HTTP verbs are:

• HTTP POST
• HTTP GET
• HTTP PUT/HTTP PATCH/HTTP POST
• HTTP DELETE.

We think of them as mapping to the acronym, CRUD (Create-Read-Update-Delete).)
We speak more on this on Create Read Update Delete in the section For SQL And HTTP REST

More Information#

There might be more information for this subject on one of the following:

• Create Read Update Delete
• HTTP
• HTTP 200
• HTTP 307
• HTTP Body
• HTTP CONNECT
• HTTP DELETE
• HTTP GET
• HTTP HEAD
• HTTP Header Field
• HTTP OPTIONS
• HTTP POST
• HTTP PUT
• HTTP Request
• HTTP TRACE
• Representational State Transfer
• Resource Action
• Verb

---

• [#1] - Request methods - based on information obtained 2016-05-21