HTTP 102 Processing vs 431 Request Header Fields Too Large
HTTP 102 (Processing) is a 1xx Informational response, while 431 (Request Header Fields Too Large) 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, 431 means that the server refuses to process the request because an individual header field or all headers collectively are too large.
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
The server refuses to process the request because an individual header field or all headers collectively are too large.
When You See It
When cookies accumulate to an excessive size, or a single header (like Authorization) is too long.
How to Fix
Reduce header sizes. Clear excessive cookies. Use shorter tokens.
Key Differences
102 is a 1xx Informational response, while 431 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 431: The server refuses to process the request because an individual header field or all headers collectively are too large.
You encounter 102 when during long-running WebDAV operations.
You encounter 431 when when cookies accumulate to an excessive size, or a single header (like Authorization) is too long.
When to Use Which
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 431 (Request Header Fields Too Large): Reduce header sizes. Clear excessive cookies. Use shorter tokens.