Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| howto:block-hackers [2026/05/17 20:18] – [Concurrent Connection Auto-Filtering] document new MaxConConnFilterSilent option (issue #1140) Claude.Ai | howto:block-hackers [2026/05/22 00:32] (current) – Add Web Server rate-limiting and auto-filter section (connection/request limiters, subnet aggregation) Claude.Ai | ||
|---|---|---|---|
| Line 107: | Line 107: | ||
| As with the failed-login auto-filter, | As with the failed-login auto-filter, | ||
| + | |||
| + | === Web Server Rate Limiting === | ||
| + | |||
| + | // | ||
| + | |||
| + | The same kind of resource-exhaustion problem affects the [[server: | ||
| + | |||
| + | To mitigate this, the Web Server supports two rate limiters plus an auto-filter: | ||
| + | * **Connection rate limiter** — caps the number of connections allowed from a client over a time period, enforced at //accept// (before a session thread or TLS handshake is created), so a flood is shed at the cheapest possible point. | ||
| + | * **Request rate limiter** — caps the number of HTTP[S] requests from a client over a time period (enforced after each request is parsed). | ||
| + | * **Subnet aggregation** — optionally counts (and filters) all clients within an IPv4/IPv6 subnet // | ||
| + | * **Auto-filter** — a client (or subnet) that exceeds a rate limit '' | ||
| + | |||
| + | Configure either via **SCFG -> Servers -> Web Server -> Rate Limiting...** or by editing the '' | ||
| ===== See Also ===== | ===== See Also ===== | ||