-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Max header size of 8KB is a breaking change #24731
Comments
bnoordhuis
added
duplicate
Issues and PRs that are duplicates of other issues or PRs.
http
Issues or PRs related to the http subsystem.
labels
Nov 29, 2018
Sorry for this and thanks for the quick answer :) |
katedee
added a commit
to cds-snc/cra-claim-tax-benefits
that referenced
this issue
Jul 24, 2019
Previously we were getting either a generic 400 error every once in awhile, or on my end, the more specific 431 error. Node before had a default header size allowance of 80kb, but changed it to 8kb (nodejs/node#24731). This was causing issues for our app, and forcing us to clear cache regularly. For our purposes now, I've bumped that limit up to 40kb.
tecfu
added a commit
to tecfu/koa
that referenced
this issue
Dec 26, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have just noticed an issue in production due to the latest Security release, especially this commit: a8532d4d23
On our website, we have pretty big cookies in some scenarios (it might not be good indeed) and we have been facing many 400 http errors since yesterday.
After investigation, we noticed that the 8KB maximum size was the issue. In my opinion, this is a breaking change.
What do you think?
The text was updated successfully, but these errors were encountered: