Accept-Patch
The Accept-Patch
response HTTP header advertises which media-type the server is able to understand in a PATCH request.
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.
Note:
- 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
http
Accept-Patch: application/example, text/example
Accept-Patch: text/example;charset=utf-8
Accept-Patch: application/merge-patch+json
Directives
None
Examples
http
Accept-Patch: application/example, text/example
Accept-Patch: text/example;charset=utf-8
Accept-Patch: application/merge-patch+json
Specifications
Specification |
---|
RFC 5789 # section-3.1 |
Browser compatibility
Browser compatibility is not relevant for this header (header is sent by server, and the specification does not define client behavior).
See also
- Http method
PATCH
- HTTP Semantic and context RFC 7231, section 4.3.4: PUT