Menu

1 / 2

WAF and rate limiting basics: what they can and cannot stop, and why they buy time rather than replace updates

DEV Community: php·Susumu Takahashi·8 days ago
#KqRM2n8q
#devto#dev#requests#rate#limiting
Reading 0:00
15s threshold

You may have seen advice like "just install a WAF and you are fine." But a WAF (Web Application Firewall) and rate limiting are filters that sit in front of your site . They do not repair the weakness inside it. This article explains what each one does, what it is good and bad at, and what is easy to miss after you turn it on. We then place both in the right role for vulnerabilities: a way to buy time until you can update . Features differ greatly by product and contract, so this stays at the level of general principles.

What a WAF is: a reception desk in front of the site

A WAF inspects the contents of each incoming request and decides whether to let it through or stop it . Think of a reception desk at the entrance of your site.

It can live in several places:

Cloud-based (in front of a CDN or similar) : filters requests before they reach your site, running on the provider's network

Server-side feature : some hosting providers offer one.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.