This is an automated email from the ASF dual-hosted git repository.

markt pushed a commit to branch 10.1.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git


The following commit(s) were added to refs/heads/10.1.x by this push:
     new 22f938bdc0 Fix name of attribute in Javadoc
22f938bdc0 is described below

commit 22f938bdc0d488afb19fa7e86b5623556d7828f2
Author: Mark Thomas <ma...@apache.org>
AuthorDate: Mon Dec 16 09:39:04 2024 +0000

    Fix name of attribute in Javadoc
---
 java/org/apache/catalina/filters/RateLimitFilter.java | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/java/org/apache/catalina/filters/RateLimitFilter.java 
b/java/org/apache/catalina/filters/RateLimitFilter.java
index b7a4b23c2c..8e07ca8182 100644
--- a/java/org/apache/catalina/filters/RateLimitFilter.java
+++ b/java/org/apache/catalina/filters/RateLimitFilter.java
@@ -42,11 +42,11 @@ import org.apache.tomcat.util.res.StringManager;
  * the bucket time ends and a new bucket starts.
  * </p>
  * <p>
- * The RateLimiter implementation can be set via the <code>className</code> 
init param. The default implementation,
- * <code>org.apache.catalina.util.FastRateLimiter</code>, is optimized for 
efficiency and low overhead so it converts
- * some configured values to more efficient values. For example, a 
configuration of a 60 seconds time bucket is
- * converted to 65.536 seconds. That allows for very fast bucket calculation 
using bit shift arithmetic. In order to
- * remain true to the user intent, the configured number of requests is then 
multiplied by the same ratio, so a
+ * The RateLimiter implementation can be set via the 
<code>rateLimitClassName</code> init param. The default
+ * implementation, <code>org.apache.catalina.util.FastRateLimiter</code>, is 
optimized for efficiency and low overhead
+ * so it converts some configured values to more efficient values. For 
example, a configuration of a 60 seconds time
+ * bucket is converted to 65.536 seconds. That allows for very fast bucket 
calculation using bit shift arithmetic. In
+ * order to remain true to the user intent, the configured number of requests 
is then multiplied by the same ratio, so a
  * configuration of 100 Requests per 60 seconds, has the real values of 109 
Requests per 65 seconds. You can specify a
  * different class as long as it implements the 
<code>org.apache.catalina.util.RateLimiter</code> interface.
  * </p>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to