HTTP 100 Continue vs 530 Site Frozen
HTTP 100 (Continue) is a 1xx Informational response, while 530 (Site Frozen) is a 5xx Server Error response. 100 indicates that the server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected. In contrast, 530 means that cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
Description
The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
When You See It
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
How to Fix
This is an interim response — no fix needed. The client should continue sending the request body.
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
100 is a 1xx Informational response, while 530 is a 5xx Server Error response.
HTTP 100: The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
HTTP 530: Cloudflare-specific. Used by Pantheon hosting to indicate a frozen site.
You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
You encounter 530 when when a site on Pantheon hosting has been frozen due to inactivity.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 530 (Site Frozen): Reactivate the site on the hosting platform.