This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
HTTP Method
HTTP Method

Version management

Difference between version and

At line 1 added 55 lines
!!! Overview[1]
[{$pagename}] (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]
[{$pagename}]
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.
%%zebra-table
%%sortable
%%table-filter
||HTTP Method||RFC||Request Has [Body|HTTP Body]||Response Has [Body|HTTP Body]||Safe||[Idempotent]||[Cacheable|[Cache-Control]]
|[GET|HTTP GET]|[RFC 7231]|%%(color:red)No%%|{{Yes}}|{{Yes}}|{{Yes}}|{{Yes}}
|[HEAD|HTTP HEAD]|[RFC 7231]|%%(color:red)No%%|%%(color:red)No%%|{{Yes}}|{{Yes}}|{{Yes}}
|[POST|HTTP POST]|[RFC 7231]|{{Yes}}|{{Yes}}|%%(color:red)No%%|%%(color:red)No%%|{{Yes}}
|[PUT|HTTP PUT]|[RFC 7231]|{{Yes}}|{{Yes}}|%%(color:red)No%%|{{Yes}}|%%(color:red)No%%
|[DELETE|HTTP DELETE]|[RFC 7231]|%%(color:red)No%%|{{Yes}}|%%(color:red)No%%|{{Yes}}|%%(color:red)No%%
|[CONNECT|HTTP CONNECT]|[RFC 7231]|{{Yes}}|{{Yes}}|%%(color:red)No%%|%%(color:red)No%%|%%(color:red)No%%
|[OPTIONS|HTTP OPTIONS]|[RFC 7231]|%%(color:red)No%%|{{Yes}}|{{Yes}}|{{Yes}}|%%(color:red)No%%
|[TRACE|HTTP TRACE]|[RFC 7231]|%%(color:red)No%%|{{Yes}}|{{Yes}}|{{Yes}}|%%(color:red)No%%
|[PATCH|HTTP PATCH]|[RFC 5789]|{{Yes}}|{{Yes}}|%%(color:red)No%%|%%(color:red)No%%|{{Yes}}
/%
/%
/%
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|Create Read Update Delete#section-Create+Read+Update+Delete-CreateReadUpdateDeleteForSQLAndHTTPREST1]
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Request methods|Wikipedia:Hypertext_Transfer_Protocol#Request_methods|target='_blank'] - based on information obtained 2016-05-21
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop