smallwebwaf

sneak/smallwebwaf

Fork 0

Files

T

History

sneak 7967d6396f

check / check (push) Failing after 5m50s

Details

rproxy tests give a loaded host time before their limits run out (closes #185 )

Four rproxy tests set a time limit of a second or less, and each needed a
step done before that limit ran out. On a loaded host the limit ran out
first, rproxy answered as SPEC.md says it should, and the test failed. Each
of these limits is now 3 seconds:

- TestAnAppTooSlowToFinishItsAnswerIsCutOff, which now also checks that the
  visitor got the app's 200 and the start of its answer;
- TestAVisitorTooSlowToTakeTheAnswerIsCutOff;
- TestAVisitorThatStopsSendingGetsAnAnswerRProxyGivesByTheDeadline;
- TestAReportServeWAFLeavesUnansweredIsDroppedAtTheTimeLimit.

Judgement call: tests whose limits already give 2 seconds or more are left as
they are.

Model: opus-5-5

2026-11-05 12:55:08 +00:00

bodies.go

rproxy, the proxy in front of each app, asks servewaf and fails open (closes #171 )

2026-11-05 06:32:08 +01:00

client.go

rproxy, the proxy in front of each app, asks servewaf and fails open (closes #171 )

2026-11-05 06:32:08 +01:00

limits_test.go

rproxy tests give a loaded host time before their limits run out (closes #185 )

2026-11-05 12:55:08 +00:00

question_test.go

rproxy and servewaf replace the one-process smallwebwaf (closes #172 , closes #165 )