SPEC: the worst-case request is refused only if it takes over 500 ms

"Answering in time" said waf refuses the slowest request a visitor can
send after 500 milliseconds. Its inspection takes under a second, which
can be under 500 milliseconds, and then it is not refused.

Model: opus-5-5
This commit is contained in:
clawbot committed 2026-11-17 04:48:10 +00:00
1 parent b0a06aac63
commit 7904647254
1 file changed
+5 -5
+5 -5
View File
@@ -2537,11 +2537,11 @@ body can add up to more than the body. From 1 KiB of JSON, Coraza makes at most
A request can reach all of these at once. At paranoia level 4, with no rule A request can reach all of these at once. At paranoia level 4, with no rule
switched off, the Core Rule Set takes under a second on one core of a current switched off, the Core Rule Set takes under a second on one core of a current
server to inspect it. `waf` refuses such a request after 500 milliseconds. server to inspect it. `waf` refuses it if the inspection takes over 500
Coraza cannot stop an inspection part-way, so the inspection runs to its end milliseconds. Coraza cannot stop an inspection part-way, so the inspection runs
with nobody waiting for it. These limits keep one request from holding a to its end with nobody waiting for it. These limits keep one request from
processor for more than about a second. Enough such requests at once can still holding a processor for more than about a second. Enough such requests at once
overload `waf` past `SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS`. can still overload `waf` past `SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS`.
### The report ### The report