How do I fix a 428 Precondition Required?
Fetch the resource first, take its ETag, and send it in an If-Match header on your update. That proves you are editing the version you last saw.
The server requires a conditional request, to prevent lost updates. 428 belongs to the 4xx client error class and is defined in RFC 6585.
Loading the workbench.
The server requires a conditional request, to prevent lost updates. The code is registered with IANA and defined in RFC 6585.
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 428 must treat it like 400.
428 Precondition Required, from RFC 6585, means the server insists that this request be conditional. It is used to prevent lost updates: an API requires If-Match on PUT, PATCH, or DELETE so that clients cannot blindly overwrite a resource they have not fetched recently. Services with concurrent editing, such as document stores and configuration APIs, use it to force optimistic locking.
Clients should GET the resource, read its ETag, and send it back in If-Match on the modifying request. If the resource changed meanwhile, the server will then answer 412 and the client can merge. Servers should explain in the body which conditional header is required, and should not cache 428 responses. Document the requirement so client developers know to fetch before updating.
HTTP/1.1 428 Precondition Required
Content-Type: application/json
Cache-Control: no-store428 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.
Fetch the resource first, take its ETag, and send it in an If-Match header on your update. That proves you are editing the version you last saw.
428 means you sent no precondition when one is required. 412 means you sent one and it turned out to be false.
Yes. 428 is a client error response: the problem is in the request, so repeating it unchanged will usually fail again.
No. Caches store a 428 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.