4×× Client Error
431 Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields.
It can be used both when the set of request header fields in total is too large, and when a single header field is at fault. In the latter case, the response representation SHOULD specify which header field was too large.
For example:
HTTP/1.1 431 Request Header Fields Too Large
Content-Type: text/html
Request Header Fields Too Large
The "Example" header was too large.
Responses with the 431 status code MUST NOT be stored by a cache.
Source: RFC6585 Section 5
431 Code References
Symfony HTTP Status Constant Response::HTTP_REQUEST_HEADER_FIELDS_TOO_LARGE
431 Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large. The request MAY be resubmitted after reducing the size of the request header fields.
It can be used both when the set of request header fields in total is too large, and when a single header field is at fault. In the latter case, the response representation SHOULD specify which header field was too large.
For example:
HTTP/1.1 431 Request Header Fields Too Large
Content-Type: text/html
Request Header Fields Too Large
The "Example" header was too large.
Responses with the 431 status code MUST NOT be stored by a cache.
Source: RFC6585 Section 5
431 Code References
Symfony HTTP Status Constant Response::HTTP_REQUEST_HEADER_FIELDS_TOO_LARGE
No comments:
Post a Comment