WhereGoes

412 Precondition Failed

4xx client error

A conditional header such as If-Match or If-Unmodified-Since evaluated false against the current resource, so the server skipped performing the request.

Common causes

  • The ETag changed because the file was edited after the client fetched it.
  • A stale If-Unmodified-Since date.
  • Concurrent deployments changed the resource mid-flow.

How to fix it

  • Refetch the resource and retry with the current validator.
  • Keep validators stable across deployments where the body is unchanged.
  • Return the current ETag in the 412 response so the client can recover.

What it means for redirects and SEO

Conditional-request failure means crawlers refetch instead of reusing cache, wasting bandwidth. ETag mismatches after deploys are a cause. Keep validators stable across releases.

Related codes