HTTP 400 Bad Request vs 530 Site Frozen
HTTP 400 (Bad Request) is a 4xx Client Error response, while 530 (Site Frozen) is a 5xx Server Error response. 400 indicates that the server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing. In contrast, 530 means that cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
Description
The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
When You See It
When sending malformed JSON, missing required fields, or invalid query parameters.
How to Fix
Check the request body format, validate all required fields, and ensure proper encoding.
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
400 is a 4xx Client Error response, while 530 is a 5xx Server Error response.
HTTP 400: The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
HTTP 530: Cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
You encounter 400 when when sending malformed JSON, missing required fields, or invalid query parameters.
You encounter 530 when when a site on Pantheon hosting has been frozen due to inactivity.
When to Use Which
For 400 (Bad Request): Check the request body format, validate all required fields, and ensure proper encoding. For 530 (Site Frozen): Reactivate the site on the hosting platform.