Remove logging of debug information when bad "L" param was discovered #551
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
Logging debug_backtrace() can cause log flooding.
|
Related issue: #549 |
Open
|
+1. debug_backtrace() is not helping anyone and generates megabytes of data for each log entry. |
|
That would be a good thing to merge this. +1 |
Don't talk for anyone, please. I had two clients, whom it actually helped. |
|
Fixed here |
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.
As some search engine bots visit our site with an invalid "L" param every few hours, our typo3temp logfile grew up to several GB. This is caused by logging the debug_backtrace() call, which should be removed.