这篇翻译不完整。请帮忙从英语翻译这篇文章。
服务器使用 HTTP 响应头 Accept-Patch 通知浏览器请求的媒体类型(media-type)可以被服务器理解。
Accept-Patch in response to any method means that PATCH is allowed on the resource identified by the Request-URI. Two common cases lead to this:
A server receiving a PATCH request with an unsupported media type could reply with 415 Unsupported Media Type and an Accept-Patch header referencing one or more supported media types.
-
An IANA registry maintains a complete list of official content encodings.
- Two others content encoding,
bzipandbzip2, are sometimes used, though not standard. They implement the algorithm used by these two UNIX programs. Note that the first one was discontinued due to patent licensing problems.
| 头部类型 | Response header |
|---|---|
| Forbidden header name（禁止修改的 HTTP 头） | yes |
语法
Accept-Patch: application/example, text/example Accept-Patch: text/example;charset=utf-8 Accept-Patch: application/merge-patch+json
指令
(无)
示例
Accept-Patch: application/example, text/example Accept-Patch: text/example;charset=utf-8 Accept-Patch: application/merge-patch+json
规范
| Specification | Title |
|---|---|
| RFC 5789, section 2.2: Accept-Patch | HTTP PATCH |
浏览器兼容性
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
No compatibility data found. Please contribute data for "http.headers.Accept-Patch" (depth: 1) to the MDN compatibility data repository.
参见
- Http method
PATCH - HTTP Semantic and context RFC 7231, section 4.3.4: PUT