HTTPD default 8Kb header limit check, to avoid 500 Internal Server Error#63
Open
dulldusk wants to merge 1 commit intoccampbell:masterfrom
Open
HTTPD default 8Kb header limit check, to avoid 500 Internal Server Error#63dulldusk wants to merge 1 commit intoccampbell:masterfrom
dulldusk wants to merge 1 commit intoccampbell:masterfrom
Conversation
The HTTP spec does not define a limit, however many servers do by default: Apache 2.0, 2.2: 8K nginx: 4K - 8K IIS: varies by version, 8K - 16K Tomcat: varies by version, 8K - 48K(?!) Ans it is not just with ChormePHP. Some user agents and some requests just get too big for web server defaults. It seems like a silly problem to run into, but it keeps happening.
This was referenced May 15, 2019
|
@dulldusk I contributed some modern code fixes to your branch for this project. I have also merged your awesome PR on my official fork of this project: phpexpertsinc/chromephp. Cheers! And thanks for all of yoru wonderful work, even tho it's been years! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The HTTP spec does not define a limit, however many servers do by
default:
Apache 2.0, 2.2: 8K
nginx: 4K - 8K
IIS: varies by version, 8K - 16K
Tomcat: varies by version, 8K - 48K(?!)
Ans it is not just with ChormePHP.
Some user agents and some requests just get too big for web server
defaults.
It seems like a silly problem to run into, but it keeps happening.