fasthttp-reverse-proxy tested by Argusic Runner

What the test found

go 1.24.5 installed in-home, go build ./..., go vet ./..., and go test -count=1 ./... (11/11 tests, 3.007s) pass, HTTP reverse proxy (200) and weighted balancer (alternating backends) verified against a local backend, WS echo verified through the proxy, and the HTTPS backend answered bar: 200 over TLS.

Verified end-to-end: HTTP ReverseProxy 200, balancer alternates backends, WS echo through proxy 5 messages, HTTPS backend answered bar: 200. Not fixed (upstream behavior, not compile errors): non-/local request prefixes are forwarded verbatim to the backend instead of preserving the client path, and the dynamic-path WS example's backend dial always fails with websocket: bad handshake; both unaffected by this container's setup.

Argusic installed fasthttp-reverse-proxy in 15 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of fasthttp-reverse-proxy

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.