400 Bad Request: Request Header Or Cookie Too Large
The server rejected the request because its headers, usually accumulated cookies, are bigger than it allows.
400 Bad Request Request Header Or Cookie Too LargeRequest Header Or Cookie Too LargeBad Request - Request Too LongHTTP Error 400. The size of the request headers is too long. Meaning
Browsers send every cookie for the domain with each request. When their total passes the server limit (often 8 KB) you get this 400 until you clear cookies. Fix by deleting site cookies, trimming what the app stores in cookies, and raising large_client_header_buffers / LimitRequestFieldSize if needed.
Common causes
- Too many or oversized cookies for the domain
- Tracking/session cookies piling up on subdomains
- JWT or session data stored in a cookie
- Server header buffer too small
- Very long query string or Authorization header
⚡ Quick fix
- Clear cookies for the site and reload
- Store big data server-side, not in cookies
- Raise server header limits (nginx
large_client_header_buffers, ApacheLimitRequestFieldSize)
Detailed fix by platform
Nginx
large_client_header_buffers 4 16k;
How to diagnose
- Cookies — Very large?
- Server limit — Too small?
- Data in cookie — Needed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026