RFC 7231 - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content https://tools.ietf.org/html/rfc7231#section-4
HTTP request methods - HTTP | MDN https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods
HTTP request methods
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 to 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.
GET
- The
GET
method requests a representation of the specified resource. Requests usingGET
should only retrieve data. HEAD
- The
HEAD
method asks for a response identical to that of aGET
request, but without the response body. POST
- The
POST
method is used to submit an entity to the specified resource, often causing a change in state or side effects on the server. PUT
- The
PUT
method replaces all current representations of the target resource with the request payload. DELETE
- The
DELETE
method deletes the specified resource. CONNECT
- The
CONNECT
method establishes a tunnel to the server identified by the target resource. OPTIONS
- The
OPTIONS
method is used to describe the communication options for the target resource. TRACE
- The
TRACE
method performs a message loop-back test along the path to the target resource. PATCH
- The
PATCH
method is used to apply partial modifications to a resource.
Specifications
Specification | Title | Comment |
---|---|---|
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. |
Browser compatibility
No compatibility data found for http/methods
.
Check for problems with this page or contribute missing data to mdn/browser-compat-data.
See also
HTTP 请求方法
规范
HTTP 定义了一组请求方法, 以表明要对给定资源执行的操作。指示针对给定资源要执行的期望动作. 虽然他们也可以是名词, 但这些请求方法有时被称为HTTP动词. 每一个请求方法都实现了不同的语义, 但一些共同的特征由一组共享:: 例如一个请求方法可以是 safe, idempotent, 或 cacheable (en-US).
GET
- GET方法请求一个指定资源的表示形式. 使用GET的请求应该只被用于获取数据.
HEAD
- HEAD方法请求一个与GET请求的响应相同的响应,但没有响应体.
POST
- POST方法用于将实体提交到指定的资源,通常导致在服务器上的状态变化或副作用.
PUT
- PUT方法用请求有效载荷替换目标资源的所有当前表示。
DELETE
- DELETE方法删除指定的资源。
CONNECT
- CONNECT方法建立一个到由目标资源标识的服务器的隧道。
OPTIONS
- OPTIONS方法用于描述目标资源的通信选项。
TRACE
- TRACE方法沿着到目标资源的路径执行一个消息环回测试。
PATCH
- PATCH方法用于对资源应用部分修改。
规范 | 标题 | 注解 |
---|---|---|
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. |
浏览器兼容性
{{Compat}}