431 Request Header Fields Too Large
This is an educational reference page about HTTP 431 Request Header Fields Too Large. The page itself is served as 200 OK so it can be indexed as HTTP documentation.
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
Specification
Registered in the IANA HTTP Status Code Registry as Request Header Fields Too Large. Defined in RFC 6585, Section 5.
Header and content rules
What RFC 6585 says about a 431 response, quoted from the RFC. The 4xx class rules also apply.
- SHOULD (server; content): Name the header field that was too large. When: A single header field is too large. Table row
In the latter case, the response representation SHOULD specify which header field was too large. RFC 6585 §5
- MUST NOT (cache; storage): Do not store the response. Table row
Responses with the 431 status code MUST NOT be stored by a cache. RFC 6585 §5
The same rules are in the response obligations table and its JSON.