filter.d/squid.conf: Improve existing failregexes against bot crawlers #2273
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
- recognizes failures from bot crawlers (eg. HTTP error code 400)
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.
Before submitting your PR, please review the following checklist:
against 0.9.x series, choose
masterbranchfailregexfor filterXwith sample log lineswithin
fail2ban/tests/files/logs/XfileCurrent filter for Squid Proxy does not detect failures from bots trying to crawl on the proxy itself. This mostly happens if the proxy is set to listen on ports normally used for web servers (eg: port 80 and 443).