HTTP defines a set of request methods to indicate the desired action to be performed for a given resource. Although they can also be nouns, these request methods are sometimes referred as HTTP verbs. Each of them implements a different semantic, but some common features are shared by a group of them: e.g. a request method can be safe, idempotent, or cacheable.
GETmethod requests a representation of the specified resource. Requests using
GETshould only retrieve data.
HEADmethod asks for a response identical to that of a
GETrequest, but without the response body.
POSTmethod is used to submit an entity to the specified resource, often causing a change in state or side effects on the server.
PUTmethod replaces all current representations of the target resource with the request payload.
DELETEmethod deletes the specified resource.
CONNECTmethod establishes a tunnel to the server identified by the target resource.
OPTIONSmethod is used to describe the communication options for the target resource.
TRACEmethod performs a message loop-back test along the path to the target resource.
PATCHmethod is used to apply partial modifications to a resource.
|RFC 7231, section 4: Request methods||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content||Specifies GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE.|
|RFC 5789, section 2: Patch method||PATCH Method for HTTP||Specifies PATCH.|
To contribute to this compatibility data, please write a pull request against this file: https://github.com/mdn/browser-compat-data/blob/master/http/methods.json.
No compatibility data found. Please contribute data for "http/methods" (depth: 1) to the MDN compatibility data repository.