HTTP PUT flood
Update-oriented REST traffic replacing or overwriting resources. Tests idempotency handling and storage write paths.
How it works
- Full resource body sent with PUT method.
- Storage and validation cost per request is typically higher than GET.
- Useful for API gateway and object-store limit testing.
Packet flow (illustrative)
Engarde node Target
→TCP established
→METHOD /resource/id HTTP/1.1
→Entity body (write path)
Illustrative flow — not a live capture.
Focus Write / update path
Engarde PUT mode
Layer L7
What to watch in Engarde
- 5xx and timeout on update endpoints.
- Lock contention on shared resources.
Running this simulation
Enable PUT in Engarde DDoS against authorized API endpoints; compare with GET baseline reports.
Mitigation perspective
Method-specific rate limits and payload size caps at API gateway.