Accept-Patch

ジャンプ先:
  1. Syntax
  2. Directives
  3. Examples
  4. Specifications
  5. Browser compatibility
  6. See also

この記事はまだボランティアによって 日本語 に翻訳されていません。ぜひ MDN に参加して翻訳を手伝ってください！
この記事を English (US) で読むこともできます。

The Accept-Patch response HTTP header advertises which media-type the server is able to understand.

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.

 

Notes:

  • An IANA registry maintains a complete list of official content encodings.

  • Two others content encoding, bzip and bzip2, 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.
Header type Response header
Forbidden header name yes

Syntax

Accept-Patch: application/example, text/example
Accept-Patch: text/example;charset=utf-8
Accept-Patch: application/merge-patch+json

Directives

None

Examples

Accept-Patch: application/example, text/example

Accept-Patch: text/example;charset=utf-8

Accept-Patch: application/merge-patch+json

Specifications

Specification Title
RFC 5789, section 2.2: Accept-Patch HTTP PATCH

Browser compatibility

No compatibility data found. Please contribute data for "http.headers.Accept-Patch" (depth: 1) to the MDN compatibility data repository.

See also

ドキュメントのタグと貢献者

タグ: 
このページの貢献者: ioggstream, jswisher
最終更新者: ioggstream,