From 0f892a893dd5aaca42301a4b365898cb779086ea Mon Sep 17 00:00:00 2001 From: Emmanuel Ferdman Date: Fri, 1 Nov 2024 15:06:37 +0200 Subject: [PATCH] Update DoS filter reference (#1920) Signed-off-by: Emmanuel Ferdman --- site/content/guides/clustering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/guides/clustering.md b/site/content/guides/clustering.md index dc91d62b7..4c21fdd79 100644 --- a/site/content/guides/clustering.md +++ b/site/content/guides/clustering.md @@ -33,6 +33,6 @@ Every node has multiple schedulers which run after a defined period of time. All ## Known constraints ### Denial-of-Service (DoS) filter -hawkBit owns the feature of guarding itself from DoS attacks, a [DoS filter](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-security-core/src/main/java/org/eclipse/hawkbit/security/DosFilter.java). It reduces the maximum number of requests per seconds which can be configured for read and write requests. +hawkBit owns the feature of guarding itself from DoS attacks, a [DoS filter](https://github.com/eclipse-hawkbit/hawkbit/blob/master/hawkbit-http-security/src/main/java/org/eclipse/hawkbit/security/DosFilter.java). It reduces the maximum number of requests per seconds which can be configured for read and write requests. This mechanism is only working for every node separately, i.e. in a cluster environment the worst-case behaviour would be that the maximum number of requests per seconds will be increased to its product if every request is handled by a different node. The same constraint exists with the validator to check if a user tried too many logins within a defined period of time.