HTTP 412 Precondition Failed vs 530 Site Frozen
HTTP 412 (Precondition Failed) is a 4xx Client Error response, while 530 (Site Frozen) is a 5xx Server Error response. 412 indicates that one or more conditions in the request headers (If-Match, If-Unmodified-Since) evaluated to false. In contrast, 530 means that cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
Description
One or more conditions in the request headers (If-Match, If-Unmodified-Since) evaluated to false.
When You See It
When using conditional requests with ETags and the resource has changed.
How to Fix
Refresh the ETag/Last-Modified value and retry with updated preconditions.
Description
Cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
When You See It
When a site on Pantheon hosting has been frozen due to inactivity.
How to Fix
Reactivate the site on the hosting platform.
Key Differences
412 is a 4xx Client Error response, while 530 is a 5xx Server Error response.
HTTP 412: One or more conditions in the request headers (If-Match, If-Unmodified-Since) evaluated to false.
HTTP 530: Cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
You encounter 412 when when using conditional requests with ETags and the resource has changed.
You encounter 530 when when a site on Pantheon hosting has been frozen due to inactivity.
When to Use Which
For 412 (Precondition Failed): Refresh the ETag/Last-Modified value and retry with updated preconditions. For 530 (Site Frozen): Reactivate the site on the hosting platform.