HTTP 207 Multi-Status vs 431 Request Header Fields Too Large
HTTP 207 (Multi-Status) is a 2xx Success response, while 431 (Request Header Fields Too Large) is a 4xx Client Error response. 207 indicates that the response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV). 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 response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV).
When You See It
In WebDAV operations that affect multiple resources simultaneously.
How to Fix
Parse the XML body to check the status of each individual resource.
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
207 is a 2xx Success response, while 431 is a 4xx Client Error response.
HTTP 207: The response body contains status information for multiple resources, in situations where multiple status codes might be appropriate (WebDAV).
HTTP 431: The server refuses to process the request because an individual header field or all headers collectively are too large.
You encounter 207 when in WebDAV operations that affect multiple resources simultaneously.
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 207 (Multi-Status): Parse the XML body to check the status of each individual resource. For 431 (Request Header Fields Too Large): Reduce header sizes. Clear excessive cookies. Use shorter tokens.