Prevent Apache 500 internal server error, truncates logs that are too… #65
Conversation
This file contains 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
|
This was addressed in the PR of my fork: PHPExpertsInc/chromephp#2. |
|
@hopeseekr, I see that your PR clobbers all of the logs. This PR attempts to keep as many logs as possible while staying under the limit. You might be interested in https://github.com/frankforte/quantumphp It works with modern versions of Firefox. I find it is faster and I prefer how the console wraps tables, etc. compared to Chrome. It can also combine logs that might be added in a loop, to prevent the logs getting large very quickly. |
|
@frankforte, thank you for your reply. this But it looks like it has been inactive/unmaintained for about few years. Anyway, thank you for your recommended related package :). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ChromePHP is meant to help developers debug. Ironically, it can cause a 500 internal server error when served from Apache if the logs are too large, which gives absolutely no information from the application about why it failed.
This commit checks the size of the header, and if it is too large, it removes some logs until it is small enough, first attempting to remove regular "status" logs, and if it is still too large, the rest of the logs. It even plays nice with the table log.