check / check (push) Waiting to run
Under heavy host load the sww tests got 503 where they expected 200 or 403: waf refused requests whose trap paths, rule files and Core Rule Set took longer than 500 ms, and rproxy gave up on waf after 2 s. waf.Params and sww.Params gain BesideLookupTimeLimit; zero keeps the 500 ms limit, so the binary is unchanged. The sww tests' run gives waf an hour, and startRProxy sets SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS to 60000, as the rproxy package's tests do. waf's own tests set the limit through the new field instead of SetBesideLookupTimeLimit, which is gone. Model: opus-5-5
5 lines
116 B
Go
5 lines
116 B
Go
package waf
|
|
|
|
// BesideLookupTimeLimit is besideLookupTimeLimit.
|
|
const BesideLookupTimeLimit = besideLookupTimeLimit
|