Skip to content

fix(dev): Raise dev header limit to 512K so localhost cookie bloat stops 431ing - #143

Merged
hoangsnowy merged 1 commit into
mainfrom
fix/header-limit-431
Aug 10, 2026
Merged

fix(dev): Raise dev header limit to 512K so localhost cookie bloat stops 431ing#143
hoangsnowy merged 1 commit into
mainfrom
fix/header-limit-431

Conversation

@hoangsnowy

Copy link
Copy Markdown
Owner

128K wasn't enough on a heavy dev box — a full localhost cookie jar overflowed Kestrel + Keycloak mid-OIDC → HTTP 431, forcing incognito/cookie-clear on every login. Both limits → 512K (lockstep). Dev-only; cloud unaffected.

Verified on the running stack: a 200KB Cookie header (hard 431 at 128K) now returns 302 from Web and 200 from Keycloak.

🤖 Generated with Claude Code

…loat stops 431ing

128 KB was still not enough on a heavily-used dev box: `localhost` shares one
cookie jar across every dev app, and a full jar overflowed both Kestrel's
MaxRequestHeadersTotalSize and Keycloak's QUARKUS_HTTP_LIMITS_MAX_HEADER_SIZE
mid-OIDC, giving HTTP 431 before auth — forcing an incognito window or a cookie
clear on every login. Both limits go to 512 KB, kept in lockstep, so the whole
round-trip survives a bloated jar in a normal browser tab. Dev/local only; cloud
requests carry no such bloat, so the larger ceiling is harmless.

Verified on the running stack: a 200 KB Cookie header (a hard 431 at 128 KB) now
returns 302 from the Web and 200 from Keycloak.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@hoangsnowy
hoangsnowy merged commit 6378fb5 into main Aug 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant