HTTP 100 Continue vs 499 Client Closed Request
HTTP 100 (Continue) is a 1xx Informational response, while 499 (Client Closed Request) is a 4xx Client 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, 499 means that a non-standard status code used by Nginx when the client closes the connection before the server responds.
説明
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.
説明
A non-standard status code used by Nginx when the client closes the connection before the server responds.
このコードが表示される場合
In Nginx logs when clients timeout or navigate away before receiving the response.
解決方法
Optimize server response times. Check for slow upstream services.
主な違い
100 is a 1xx Informational response, while 499 is a 4xx Client 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 499: A non-standard status code used by Nginx when the client closes the connection before the server responds.
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 499 when in Nginx logs when clients timeout or navigate away before receiving the response.
どちらをいつ使うか
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 499 (Client Closed Request): Optimize server response times. Check for slow upstream services.