If-Match HTTP request header makes the request conditional. For
HEAD methods, the server will send back the requested resource only if it matches one of the listed
PUT and other non-safe methods, it will only upload the resource in this case.
The comparison with the stored
ETag uses the strong comparison algorithm, meaning two files are considered identical byte to byte only. This is weakened when the
W/ prefix is used in front of the
There are two common use cases:
HEADmethods, used in combination with an
Rangeheader, it can guarantee that the new ranges requested comes from the same resource than the previous one. If it doesn't match, then a
- For other methods, and in particular for
If-Matchcan be used to prevent the lost update problem. It can check if the modification of a resource that the user wants to upload will not override another change that has been done since the original resource was fetched. If the request cannot be fulfilled, the
412(Precondition Failed) response is returned.
|Header type||Request header|
|Forbidden header name||no|
If-Match: <etag_value> If-Match: <etag_value>, <etag_value>, …
- Entity tags uniquely representing the requested resources. They are a string of ASCII characters placed between double quotes (Like
"675af34563dc-tr34") and may be prefixed by
W/to indicate that the weak comparison algorithm should be used.
- The asterisk is a special value representing any resource.
If-Match: "bfc13a64729c4290ef5b2c2730249c88ca92d82d" If-Match: W/"67ab43", "54ed21", "7892dd" If-Match: *
|RFC 7232, section 3.1: If-Match||Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests|
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.
|Feature||Android||Chrome for Android||Edge Mobile||Firefox for Android||IE Mobile||Opera Mobile||Safari Mobile|
Range Not Satisfiable