clawbot 6977ff73df Proxy timing tests outlast a hold-up of the test process (closes #53) ...

smallwebwaf starts each timeout as the request arrives, before the step
a test needs first: the upgrade answered, the app's buffers full, the
first part of an answer passed on. A hold-up of the test process longer
than the 300 ms timeout ran it out before that step. No test can make
that step come first, and in the "waiting on the app" cases it cannot
see which side smallwebwaf was waiting on, so the timeout is now 5 s,
the hold-up wantTimedOut already allows. The timeout tests set when it
must not run out goes from 10 s to 1 m to stay clear of it. The upgrade
test waits 7.5 s past the upgrade.

Judgement call: one shared value; the proxy tests take about 8 s, not 2 s.

Model: opus-5-5

2026-10-04 07:53:18 +02:00

..

bodies.go

Pass-through proxy with timeouts, size limits and a request log (closes #13)

2026-10-03 17:24:34 +02:00

client_test.go

Pass-through proxy with timeouts, size limits and a request log (closes #13)

2026-10-03 17:24:34 +02:00

client.go

Per-client request rate limits over a minute, an hour and a day (closes #43)

2026-10-04 04:24:34 +02:00

limits_test.go

Pass-through proxy with timeouts, size limits and a request log (closes #13)

2026-10-03 17:24:34 +02:00

passthrough_test.go

Proxy timing tests outlast a hold-up of the test process (closes #53)

2026-10-04 07:53:18 +02:00

proxy_test.go

Proxy timing tests outlast a hold-up of the test process (closes #53)

2026-10-04 07:53:18 +02:00

proxy.go

Per-client request rate limits over a minute, an hour and a day (closes #43)

2026-10-04 04:24:34 +02:00

ratelimits_test.go

Per-client request rate limits over a minute, an hour and a day (closes #43)

2026-10-04 04:24:34 +02:00

request.go

Per-client request rate limits over a minute, an hour and a day (closes #43)

2026-10-04 04:24:34 +02:00

timeouts_test.go

TestRequestTimeouts expects 504 when none of the body reached the app (closes #49)

2026-10-04 06:09:22 +02:00