What Is HTTP 431 Request Header Fields Too Large?
HTTP 431 Request Header Fields Too Large explained, and what it means when you see it in CI/CD and deployments.
HTTP 431 means the server refuses the request because its header fields are too large.
What it means
A 431 happens when headers (often a huge cookie or a long Authorization token) exceed the server limit.
When you see it in CI/CD
In CI, a 431 can come from oversized auth tokens or accumulated cookies. Trim headers or use a smaller token.
Key takeaways
- 431 means headers too large.
- Often an oversized token/cookie.
- Trim the headers.
Related guides
What Is HTTP 413 Payload Too Large?HTTP 413 Payload Too Large means the request body exceeds the server limit. Learn the CI fix.
What Is a Bearer Token? Whoever Holds It Gets InA bearer token grants access to anyone who presents it, sent in the Authorization header. Learn what bearer t…
What Is HTTP 400 Bad Request?HTTP 400 Bad Request means the server could not understand the request. Learn common CI causes.