What is an HTTP flood DDoS attack?
An HTTP flood is an application-layer (Layer 7) DDoS attack. Many machines send ordinary-looking HTTP GET or POST requests to a web server or API until it has no capacity left for real users. Each request is valid HTTP, so there is no malformed packet to drop. The damage comes from the work each request triggers on the server, not from the bandwidth it uses.
It is one form of an application-layer DDoS attack, and part of the wider distributed denial of service family. This entry covers how floods work and how to defend against them. It is not a guide to launching one: attacking systems you do not own is illegal.
How an HTTP flood works
- A botnet sends the traffic. Requests arrive from a large number of compromised devices or rented machines, so no single IP address stands out.
- Requests look normal. Headers, methods and URLs are valid, and the user-agent is often copied from a real browser.
- Expensive endpoints are the target. Search, filtered listings, login and recommendation calls cost the server far more than a static file, so a modest request rate can exhaust worker processes or database connections.
- Caches are bypassed. Adding a random query parameter to every URL (for example
?q=shoes&_=83721) makes each request look new, so it passes the CDN and reaches your origin.
A GET flood hits read endpoints. A POST flood hits write endpoints such as sign-up or contact forms, and is often harder on the database. Slow attacks like Slowloris and RUDY are related but work differently: they hold connections open with very little traffic rather than sending a high request rate.
Example: a flood on a search page
Take a shop whose /search endpoint runs an uncached database query. On a normal day it handles a few requests per second. During a flood, thousands of clients each request /search with a different random term. Every request misses the cache, the database connection pool fills, and checkout calls begin to time out. Browsers and apps retry, which adds load. Nothing here was "hacked": the site simply ran out of capacity, which is why the first sign is usually slow responses and rising error rates.
Why HTTP floods are hard to stop
- They resemble a traffic spike. A burst of requests from many IPs can be a campaign or a flood. Blocking too hard loses customers, blocking too little leaves you down.
- Cost is lopsided. A small request can trigger a database query and several downstream calls.
- Autoscaling can raise the bill. If you scale on request count, you may pay to serve attack traffic. Set a maximum.
How to defend against an HTTP flood
- Put an edge in front of the origin. A CDN serves cacheable content and absorbs bursts before they reach your servers.
- Use WAF rate limits. A web application firewall can count requests per source and limit those that arrive too fast. For example, AWS WAF rate-based rules aggregate requests by criteria you choose and apply an action when a limit is exceeded.
- Challenge suspicious clients. A JavaScript challenge or CAPTCHA filters bots that do not run a browser.
- Cache and normalise URLs. Ignore parameters that do not change the response so cache-busting stops working.
- Limit per session and per account, not only per IP, because a botnet rotates addresses.
- Protect expensive endpoints. Add timeouts, a circuit breaker or a cached fallback so one slow dependency does not take the whole site down.
The step-by-step plan is in how to stop DDoS attacks.
Common mistakes
- Rate limiting only by IP address.
- Setting a limit below your real peak, so a product launch triggers it.
- Caching static files but not the expensive pages behind them.
- Having no baseline, so nobody knows what "double the normal request rate" looks like.
- Waiting for customers to report the outage.
HTTP floods, load testing and monitoring
Load testing is not attack simulation and does not replace a WAF or DDoS protection. What it can do is show where your own application runs out of capacity under heavy but legitimate traffic: which endpoint slows first, and whether your limits and caching behave as designed. Only test systems you own or have written permission to test, and prefer staging. LoadFocus runs load tests with JMeter and k6 from cloud regions, and the free plan allows up to 10 virtual users. See load testing vs stress testing for how the two differ.
Monitoring catches a flood early. Alert on request rate, error rate and p95 latency against a baseline, and watch your public endpoints with API monitoring. If a limit is blocking real clients, this guide to API rate limiting helps you read the 429 responses. Cloud providers publish their own rules for DDoS simulation: AWS only permits it through approved partners or after prior approval.
FAQ: HTTP flood DDoS attacks
What is the difference between an HTTP flood and a volumetric attack?
A volumetric attack tries to fill your network bandwidth with raw traffic. An HTTP flood sends valid requests and exhausts server resources such as workers, database connections and downstream API quotas, often with far less bandwidth.
How can I tell an HTTP flood from a viral traffic spike?
Look at the shape of the traffic. Organic spikes usually concentrate on a few pages, with varied referrers, browsers and regions, and visitors who browse and convert. Floods tend to be uniform: similar user-agents, odd URLs with random parameters, no referrers and no conversions.
Does a CDN stop an HTTP flood?
It helps with cacheable content, but cache-busting parameters and dynamic endpoints still reach your origin. Combine the CDN with WAF rate limits, challenges and application-level limits.
Should I rate limit by IP or by session?
Both. IP limits catch single sources, while session or account limits catch a botnet that spreads requests across many addresses.
Can I test my site against an HTTP flood?
You can load test your own application to find its capacity limits, with authorisation and ideally on staging. A real DDoS simulation is a separate service that providers restrict, so ask your provider before running anything that imitates an attack.
Related terms
Related LoadFocus Tools
Put this concept into practice with LoadFocus, the same platform that powers everything you just read about.