Act-Ratelimit
Introduction
Act-Ratelimit is a rate limiting tool for fastapi.
It is a fork of fastapi-limiter with support for multiple Datastores and different Ratelimit strategies.
Requirements
Additional Requirements
Install
Just install from pypi
pip install act-ratelimit
You can also install the additional requirements
pip install act-ratelimit[redis]
pip install act-ratelimit[valkey]
Quick Start
Act-Ratelimit is simple to use, you need to initialize it with your preferred backend and then use the RateLimiter dependency in your routes.
import redis.asyncio as redis
from contextlib import asynccontextmanager
from act_ratelimit import ACTRatelimit
from act_ratelimit.depends import RateLimiter
from act_ratelimit.backends import RedisBackend
@asynccontextmanager
async def lifespan(_: FastAPI):
redis_backend = RedisBackend(
redis.from_url("redis://localhost:6379", encoding="utf8"), prefix="act-ratelimit-example"
)
await ACTRatelimit.init(redis_backend)
yield
await ACTRatelimit.close()
app = FastAPI(lifespan=lifespan)
@app.get("/", dependencies=[Depends(RateLimiter(times=2, seconds=5))])
async def index():
return {"msg": "Hello World"}
[!NOTE] For people coming from fastapi-limiter, the
FastAPILimiter.initmethod has changed. It now takes a backend instance instead of a redis instance.
Usage
You will first need to initialize the ACTRatelimit with a backend instance.
Other possible parameters are:
identifier- The identifier of the rate limit, default isip.callback- The callback when the rate limit is exceeded.strategy- The strategy to use for the rate limit, default isFIXED_WINDOW.
Backend
There are currently two backends pre-implemented, RedisBackend and ValkeyBackend.
RedisBackend uses the redis library to interact with a redis instance.
ValkeyBackend uses the valkey library to interact with a valkey instance.
You can also implement your own backend by inheriting from the BaseBackend class.
from act_ratelimit.backends import BaseBackend
from act_ratelimit.constants import RateLimitStrategy
class MyBackend(BaseBackend):
async def check(self, key: str, times: int, limit: int, strategy: RateLimitStrategy) -> int:
"""Check if a key has hit the rate limit.
This method should return the time in milliseconds until the rate limit resets.
If the rate limit has not been hit, it should return 0.
Args:
key: The key to check.
times: The number of times the key has to be hit to trigger the rate limit.
limit: How long the rate limit should last in milliseconds.
"""
raise NotImplementedError
async def close(self) -> None:
"""Close the connection to the backend."""
raise NotImplementedError
Strategies
There are currently three strategies available, FIXED_WINDOW, SLIDING_WINDOW and FIXED_WINDOW_ELASTIC.
[!NOTE] These Strategies need to be implemented in the backend. If you are using a custom backend, you will need to implement these strategies.
Identifier
Identifier of route limit, default is ip, you can override it such as userid and so on.
async def default_identifier(request: Request):
forwarded = request.headers.get("X-Forwarded-For")
if forwarded:
return forwarded.split(",")[0]
return request.client.host + ":" + request.scope["path"]
Callback
Callback when access is forbidden, default is raise HTTPException with 429 status code.
async def default_callback(request: Request, response: Response, pexpire: int):
"""
default callback when too many requests
:param request:
:param pexpire: The remaining milliseconds
:param response:
:return:
"""
raise HTTPException(
HTTP_429_TOO_MANY_REQUESTS, "Too Many Requests", headers={"Retry-After": str(pexpire)}
)
Multiple limiters
You can use multiple limiters in one route.
@app.get(
"/multiple",
dependencies=[
Depends(RateLimiter(times=1, seconds=5)),
Depends(RateLimiter(times=2, seconds=15)),
],
)
async def multiple():
return {"msg": "Hello World"}
Not that you should note the dependencies orders, keep lower of result of seconds/times at the first.
Rate limiting within a websocket.
While the above examples work with rest requests, FastAPI also allows easy usage of websockets, which require a slightly different approach.
Because websockets are likely to be long lived, you may want to rate limit in response to data sent over the socket.
You can do this by rate limiting within the body of the websocket handler:
@app.websocket("/ws")
async def websocket_endpoint(websocket: WebSocket):
await websocket.accept()
ratelimit = WebSocketRateLimiter(times=1, seconds=5)
while True:
try:
data = await websocket.receive_text()
await ratelimit(websocket, context_key=data) # NB: context_key is optional
await websocket.send_text(f"Hello, world")
except WebSocketRateLimitException: # Thrown when rate limit exceeded.
await websocket.send_text(f"Hello again")
License
This fork contains modifications by Act-App licensed under MIT License.
The original project remains under the Apache-2.0 License.
Metadata
Release files for act-ratelimit 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| act_ratelimit-1.0.0.tar.gz | 17.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| act_ratelimit-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.0 kB
Release files / act_ratelimit-1.0.0.tar.gz
| Download URL | act_ratelimit-1.0.0.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1dc8f16d564739fc427e1da92aa1f823b8b9eae63c09f8ede7e0f5b670a1554
|
|
BLAKE2b-256 checksum How to use checksums |
cd278cf9755c5fef1747397c9bfc78a348c3c912a542f8fe49a40e3b29f8afe0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.32.3
|
Release files / act_ratelimit-1.0.0-py3-none-any.whl
| Download URL | act_ratelimit-1.0.0-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a4eb42e2057bf8df3a6701d06ab5267fae5f34ce224300f6daf72ab1ed06ea9b
|
|
BLAKE2b-256 checksum How to use checksums |
a9689203006a65e139f3964d17ca7b7b0ee9378668a780fc0ebb6422d88a851f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.32.3
|
Security for act-ratelimit 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.