HTTP 100 Continue vs 524 A Timeout Occurred
HTTP 100 (Continue) is a 1xx Informational response, while 524 (A Timeout Occurred) 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, 524 means that cloudflare-specific. A TCP connection was established but the origin didn't respond with an HTTP response in time.
説明
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 a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
解決方法
This is an interim response — no fix needed. The client should continue sending the request body.
説明
Cloudflare-specific. A TCP connection was established but the origin didn't respond with an HTTP response in time.
このコードが表示される場合
When a request to the origin takes longer than Cloudflare's 100-second timeout.
解決方法
Optimize slow endpoints. Move long-running tasks to background jobs.
主な違い
100 is a 1xx Informational response, while 524 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 524: Cloudflare-specific. A TCP connection was established but the origin didn't respond with an HTTP response in time.
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 524 when when a request to the origin takes longer than Cloudflare's 100-second timeout.
どちらをいつ使うか
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 524 (A Timeout Occurred): Optimize slow endpoints. Move long-running tasks to background jobs.