How does If-Match prevent lost updates?
The client sends the ETag of the version it edited. If someone changed the resource meanwhile, the ETag no longer matches and the server answers 412 instead of silently overwriting their work.
An If-Match or If-Unmodified-Since condition was false. Used for optimistic locking. 412 belongs to the 4xx client error class and is defined in RFC 9110.
Loading the workbench.
An If-Match or If-Unmodified-Since condition was false. Used for optimistic locking. The code is registered with IANA and defined in RFC 9110.
Client error: the request has a problem, so it cannot be fulfilled as sent. Every code from 400 to 499 shares that general meaning, so a client that does not recognise 412 must treat it like 400.
412 Precondition Failed means a conditional header in the request evaluated to false. The usual case is optimistic locking: a client sends If-Match with the ETag it last saw, but the resource has changed since, so the server refuses to overwrite someone else's update. If-Unmodified-Since works the same way with dates. It also appears when If-None-Match: * is used to create a resource only if it does not already exist.
Clients should GET the resource again to obtain the current ETag and content, reapply or merge their change, and resend with the new validator. Servers should include the current ETag in the 412 response so the client can see what changed. Make sure ETags are strong when used with If-Match, since weak ETags never satisfy If-Match comparisons.
HTTP/1.1 412 Precondition Failed
ETag: "v18"
Content-Type: application/json412 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
curl -i.Browse every code on the HTTP status codes page.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
The client sends the ETag of the version it edited. If someone changed the resource meanwhile, the ETag no longer matches and the server answers 412 instead of silently overwriting their work.
If-Match requires the strong comparison, and a weak ETag never matches strongly. Servers must generate strong ETags for resources that support conditional updates.
Yes. 412 is a client error response: the problem is in the request, so repeating it unchanged will usually fail again.
No. Caches store a 412 only when Cache-Control or Expires explicitly allows it.
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.