Releases: Fabian123333/mod_antiddos
v0.2.1
v0.2.0
Changelog:
- performance improvements
- changed internal config structure in order to optimize performance for large scale and distributed environments with dedicated rules for different clients, by only "checking" filters that are configured for any or matching domains.
- code cleanup
v0.1.3-beta
Changelog:
- Change Domains filter to support arrays (e.g. to cover www.example.com + example.com in the same filter).
- update docs
The following features are on the wishlist and need further investigation:
Detect changing UserAgent
-> how would filters look like, and should these rules be executed multiple times?
v0.1.2-beta
Changelog:
improve filter handler to reduce performance impact when having several thousand rules, by separating post-, and pre-processing filters strictly.
implement base structure for content filters.
The following features are on the wishlist and need further investigation:
Detect changing UserAgent
-> how would filters look like, and should these rules be executed multiple times?
Change Domains filter to arrays (e.g. to cover www.example.com + example.com in the same filter).
v0.1.1-beta
Changelog:
- implement postprocessing of requests
-> Filters e.g. based on StatusCode are available, now
-> If required content based filters can be implemented easily
The following features are not available, yet:
- Auto Whiltelist of CDN-IPs
-> currently no good way of fetching all common CDNs and compare them in a way, not consuming too many ressources. One solution would be adding a generate / update job fetching common / selected CDNs and generate a regex from them (which would in most cases especially with many IPs be faster then using the build-in CharList.Contains function.
--> https://www.cloudflare.com/ips-v4
--> https://www.cloudflare.com/ips-v6
-> currently recommended to import the required IPs manually in the anti-ddos.json whitelist.
The following features are on the wishlist and need further investigation:
- Detect changing UserAgent
-> how would filters look like, and should these rules be executed multiple times?
v0.1.0-beta
The following features are not available, yet:
- Filters based on HTTP Response
-> need postprocessing of http requests, currently the protection parses requests only before they are sent to the Application - Auto Whiltelist of CDN-IPs
-> currently no good way of fetching all common CDNs and compare them in a way, not consuming too many ressources. One solution would be adding a generate / update job fetching common / selected CDNs and generate a regex from them (which would in most cases especially with many IPs be faster then using the build-in CharList.Contains function.
--> https://www.cloudflare.com/ips-v4
--> https://www.cloudflare.com/ips-v6
The following features are on the wishlist and need further investigation:
- Detect changing UserAgent
-> how would filters look like, and should these rules be executed multiple times?