From 0f66fc216abb49069f87c0dd0c9f90ecd6f3728b Mon Sep 17 00:00:00 2001 From: Marc Giffing Date: Mon, 11 Mar 2024 20:33:54 +0100 Subject: [PATCH] Support for Method level @RateLimiting annoation #250 --- README.adoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/README.adoc b/README.adoc index ef5f818b..8adf2a45 100644 --- a/README.adoc +++ b/README.adoc @@ -64,8 +64,6 @@ You have two options for rate limit configuration: adding a filter for incoming Filters are customizable components designed to intercept incoming web requests, capable of rejecting requests to halt further processing. You can incorporate multiple filters for various URLs or opt to bypass rate limits entirely for authenticated users. When the limit is exceeded, the web request is aborted, and the client receives an HTTP Status 429 Too Many Requests error. -This project supports the following filters: - This projects supports the following filters: * https://docs.oracle.com/javaee%2F6%2Fapi%2F%2F/javax/servlet/Filter.html[Servlet Filter] (Default) @@ -84,8 +82,6 @@ bucket4j.filters[0].rate-limits[0].bandwidths[0].refill-speed=intervall === Method -By annotating your method with @RateLimiting, AOP is used to intercept the method. You have full access to the method parameters to define the rate limit key or skip the rate limit on your conditions. - Utilizing the '@RateLimiting' annotation, AOP intercepts your method. This grants you comprehensive access to method parameters, empowering you to define the rate limit key or conditionally skip rate limiting with ease. [source,properties]