HTTP

HTTP 100 Continue vs 522 Connection Timed Out

HTTP 100 (Continue) is a 1xx Informational response, while 522 (Connection Timed Out) 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, 522 means that cloudflare-specific. TCP connection to the origin server timed out.

Beschreibung

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.

Wann Sie es sehen

When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.

Wie man es behebt

This is an interim response — no fix needed. The client should continue sending the request body.

Beschreibung

Cloudflare-specific. TCP connection to the origin server timed out.

Wann Sie es sehen

When the origin server is overloaded or network issues prevent connection.

Wie man es behebt

Check origin server health. Verify firewall rules. Check for network congestion.

Wesentliche Unterschiede

1.

100 is a 1xx Informational response, while 522 is a 5xx Server Error response.

2.

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.

3.

HTTP 522: Cloudflare-specific. TCP connection to the origin server timed out.

4.

You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.

5.

You encounter 522 when when the origin server is overloaded or network issues prevent connection.

Wann welchen verwenden

For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 522 (Connection Timed Out): Check origin server health. Verify firewall rules. Check for network congestion.

Mehr erfahren