extend user agent filter by "python", "wget" and "monitor" #151
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 #149
Back in #125 the user agent filter for bot detection has been reworked.
As @KittMedia already mentioned in #125 (comment) the
wget
identifier has been forgotten whilecurl
is present. Never taken care of that...Also commonly used monitoring tools like Nagios/Icinga or PRTG are not excluded. They are not "bots" in terms of crawlers/spiders, but also non-human requests which are not meant to be counted. Both contain the word "monitor(ing)" while afaik no client webbrowser contains this.
I've also added
python
, because it's quite common for analysis scripts and bots as well.Example UA strings that pass the 1.7 filter, but shouldn't:
The latter also passed the <=1.6 filter, because it contains "Windows"...