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.
-
An IANA registry maintains a complete list of official content encodings.
- Two others content encoding,
bzip
andbzip2
, 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 3.1: Accept-Patch | HTTP PATCH |
Browser compatibility
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.
See also
- Http method
PATCH
- HTTP Semantic and context RFC 7231, section 4.3.4: PUT