You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Allows clients to verify if the server will accept their request headers before
24
24
25
25
When a client includes the `Expect: 100-continue` header, is requesting a confirmation before sending the request body, prompting the server to respond immediately with either `100 Continue` to proceed or an appropriate status code (for example, 401 Unauthorized or 413 Payload Too Large) if the request is unacceptable.
26
26
27
-
### Cloudflare-specific behavior
27
+
### Cloudflare-specific information
28
28
29
29
Cloudflare uses Keep-Alive connections to maintain persistent communication between clients and servers, making the `100 Continue` response typically unnecessary, as Keep-Alive reduces overhead and eliminates the need for intermediate confirmations.
30
30
@@ -36,7 +36,7 @@ The 101 Switching Protocols status code indicates that the origin server accepts
36
36
37
37
The 101 Switching Protocols status code indicates that the server has accepted the client's request to change protocols, either by including an `Upgrade` header or through a change in the application protocol on the connection. When the `Upgrade` header is used, the server agrees to switch to a protocol higher on the client's priority list and responds with an `Upgrade` header to specify the new protocol(s). This change is assumed to benefit both the client and the server, with WebSockets being the most common use case.
38
38
39
-
### Cloudflare-specific behavior
39
+
### Cloudflare-specific information
40
40
41
41
Cloudflare supports WebSocket connections, which often involve the 101 Switching Protocols status code. The protocol switch allows clients to establish a WebSocket connection for real-time, bidirectional communication. For information about Cloudflare’s Websockets, refer to [Cloudflare Now Supports Websockets](https://blog.cloudflare.com/cloudflare-now-supports-websockets/).
42
42
@@ -48,6 +48,6 @@ Cloudflare supports WebSocket connections, which often involve the 101 Switching
48
48
49
49
The 102 Processing status code is commonly used in scenarios requiring long-running operations, such as complex database transactions or large file processing. It helps maintain the connection during extended processing times, typically exceeding 20 seconds, ensuring efficient communication between the client and server throughout the operation.
50
50
51
-
### Cloudflare-specific behavior
51
+
### Cloudflare-specific information
52
52
53
53
If Cloudflare receives a 102 Processing response, it expects a final response within 100 seconds. Failure to receive this response results in an [Error 522: Connection Timed Out](https://support.cloudflare.com/hc/articles/115003011431#522error). However, sending interim 102 Processing responses can help prevent [Error 524: A timeout error](https://support.cloudflare.com/hc/articles/115003011431#524error), ensuring that the connection remains active while the server processes the request.
0 commit comments