HTTP 431 Request Header Fields Too Large

The request headers, or a single header, are too large.

Updated

431
Request Header Fields Too Large
4xx Client error
Class
RFC 6585
Defined in

What does HTTP 431 mean?

The request headers, or a single header, are too large. Almost always caused by too many or too large cookies on a domain — for example tracking cookies piling up, or a large session stored in a cookie.

4xx Client error: The request has a problem the client can fix: wrong URL, missing credentials, bad data or too many requests.

Common causes of a 431 error

  • Oversized cookies.
  • Very long Referer or custom headers.

How to fix 431 Request Header Fields Too Large

  • Clear cookies for the site.
  • Store sessions server-side and keep cookies small.
  • Raise large_client_header_buffers (Nginx) if headers are legitimately large.

431 and SEO

Crawlers send few cookies, so they rarely see 431.

Example response

HTTP/1.1 431 Request Header Fields Too Large

Related status codes

Check which status code a URL returns with the HTTP header checker.

All HTTP status codesSearch the full list of status codes from 100 to 599 with their meanings and SEO impact.
Open the full list

Frequently asked questions

What does status code 431 mean?
431 Request Header Fields Too Large: The request headers, or a single header, are too large.
How do I fix a 431 error?
Clear cookies for the site. Store sessions server-side and keep cookies small.
Does 431 affect SEO?
Crawlers send few cookies, so they rarely see 431.