You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you need rules to whitelist IP address range or Countries simply...
74
79
75
-
```php
76
-
Firewall::whitelistIp('101.1.1.254');
77
-
```
78
-
79
-
or
80
-
81
-
```php
82
-
Firewall::whitelistCountry('US');
83
-
```
80
+
These can be added to the configuration file bot-licker.php
84
81
85
82
### Automated rules
86
83
87
-
Are you tired of seeing bots trying to hit .env or phpinfo.php in your logs? You can now zap these IPs instantly with, you can pass an option Carbon instance if you wish to have an expiry on the rule, otherwise it runs indefinitely.
84
+
Are you tired of seeing bots trying to hit .env or phpinfo.php in your logs? You can build a custom ruleset which matches a string in the request URI. And then perform an action on the user arriving from this IP (or Country).
This will match any incoming request URIs with phpinfo.php in the URL ie https://domain.com/phpinfo.php and then ban the IP address for a year.
91
+
93
92
### Extending BotLicker with new providers
94
93
95
-
Currently only Cloudflare is supported, however you can easily implement the ProviderContract and generate the corresponding methods for other WAFs. Once you have created your provider, simply inject it into the `setProvider()`
94
+
Currently only Cloudflare is supported, however you can easily implement the ProviderContract and generate the corresponding methods for other WAFs. Once you have created your provider, simply inject it into the `setProvider()` or replace the default provider in the configuration file.
Currently the package perform simply bans/unbans etc. In the next iteration, ban duration will be also be added in order for some rules to be removed after X timeperiod. ie
0 commit comments