[3.0] Dont let bots flood logs#9145
Merged
jdarwood007 merged 1 commit intoSimpleMachines:release-3.0from Mar 12, 2026
Merged
Conversation
Signed-off-by: Shawn Bulen <bulens@pacbell.net>
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
2 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.
Fixes #9142
3.0 version of #9144 . More discussion may be found there.
Just don't log "Unable to verify referring URL" errors. This gives a handle for bots to flood your logs. Plus, I'm not sure the info is usable or actionable. Note also that the other similar session errors throughout this logic are not logged.
I kept the one a few lines below this as logged - that condition appears to be more of a trap for an internal issue. So it's kept, for now...