428 Precondition Required
4xx client error
The server requires a conditional request, such as If-Match, to avoid lost updates, and rejects unconditional writes to the resource.
Common causes
- The client sent a write without any conditional header.
- An update endpoint enforces optimistic concurrency.
- A bulk sync omits version tokens.
How to fix it
- Fetch the resource first and send If-Match with its ETag.
- Document the required headers for every write endpoint.
- Return a clear message naming the precondition the client must supply.
What it means for redirects and SEO
Lost-update protection means unconditional writes fail, which crawlers trigger when posting. The page read path usually returns 200. Document the required conditional headers.