@@ -16,8 +16,9 @@ time, but you can use them for your own features too.
1616 By definition, the Symfony rate limiters require Symfony to be booted
1717 in a PHP process. This makes them not useful to protect against `DoS attacks `_.
1818 Such protections must consume the least resources possible. Consider
19- using `Apache mod_ratelimit `_, `NGINX rate limiting `_ or proxies (like
20- AWS or Cloudflare) to prevent your server from being overwhelmed.
19+ using `Apache mod_ratelimit `_, `NGINX rate limiting `_,
20+ `Caddy HTTP rate limit module `_ (also supported by FrankenPHP)
21+ or proxies (like AWS or Cloudflare) to prevent your server from being overwhelmed.
2122
2223.. _rate-limiter-policies :
2324
@@ -536,6 +537,7 @@ you can use a specific :ref:`named lock <lock-named-locks>` via the
536537`DoS attacks` :https://cheatsheetseries.owasp.org/cheatsheets/Denial_of_Service_Cheat_Sheet.html
537538.. _`Apache mod_ratelimit` :https://httpd.apache.org/docs/current/mod/mod_ratelimit.html
538539.. _`NGINX rate limiting` :https://www.nginx.com/blog/rate-limiting-nginx/
540+ .. _`Caddy HTTP rate limit module` :https://github.com/mholt/caddy-ratelimit
539541.. _`token bucket algorithm` :https://en.wikipedia.org/wiki/Token_bucket
540542.. _`PHP date relative formats` :https://www.php.net/manual/en/datetime.formats.php#datetime.formats.relative
541543.. _`Race conditions` :https://en.wikipedia.org/wiki/Race_condition