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
Initial documents: what smallwebwaf is and why, the proposed feature list, the design spec with the rule file format and the open design questions, and the survey of existing tools.
Model: fable-5-1
sneak