startRProxyProcess still ran rproxy at the 2-second default of SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS. On a busy host, TestRProxyAsksAWAFThatSpeaksHTTP2OverHTTP1 could then get the app's 200 instead of waf's 403, as startRProxy's tests could before. Model: opus-5-5