HTTP 102 Processing vs 499 Client Closed Request
HTTP 102 (Processing) is a 1xx Informational response, while 499 (Client Closed Request) is a 4xx Client Error response. 102 indicates that the server has received and is processing the request, but no response is available yet. Prevents the client from timing out. In contrast, 499 means that a non-standard status code used by Nginx when the client closes the connection before the server responds.
Description
The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
When You See It
During long-running WebDAV operations.
How to Fix
Wait for the final response. This is an interim status to prevent timeouts.
Description
A non-standard status code used by Nginx when the client closes the connection before the server responds.
When You See It
In Nginx logs when clients timeout or navigate away before receiving the response.
How to Fix
Optimize server response times. Check for slow upstream services.
Key Differences
102 is a 1xx Informational response, while 499 is a 4xx Client Error response.
HTTP 102: The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
HTTP 499: A non-standard status code used by Nginx when the client closes the connection before the server responds.
You encounter 102 when during long-running WebDAV operations.
You encounter 499 when in Nginx logs when clients timeout or navigate away before receiving the response.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 499 (Client Closed Request): Optimize server response times. Check for slow upstream services.