fasthttp-reverse-proxy
reverse http / websocket proxy based on fasthttp
Runssource: GitHubGoMITcommit 3b0dcb225a9f
Go, MIT licensed. The project labels itself: fasthttp, go, http proxy, lib, reverse proxy and websocket proxy.
fasthttp-reverse-proxy runs. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
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.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- go build ./.../go test ./... failed: examples/https-reverse-proxy had two func main in one package (tlscert.go + proxy.go)6 minutes
- no Go toolchain in the container4 minutes
- the plain HTTP example hardcoded localhost:8080, which in this container resolved to the stale TLS backend, so the demo proxy returned 5004 minutes
- go vet flagged benchmark/ws_proxy_benchmark.go:44: misuse of unbuffered os.Signal channel1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl -sS -o /tmp/pb -w '%{http_code}' http://127.0.0.1:8081/local/hello?x=1 returned 200; go test -count=1 ./... exited 0, root package ok 3.007s, 11 test funcs pass; go build ./... and go vet ./... exited 0
- Model tokens used
- 560,272
- Exact commit tested
- 3b0dcb225a9f
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Error 2 (`go vet`): `benchmark/ws_proxy_benchmark.go:44` unbuffered signal channel passed to `sig… - Error 3: no Go toolchain in container. Fixed (user install in `$HOME`): downloaded `go1.24.5.linu… - Error 4: example plain HTTP proxy hardcoded `localhost:8080`, which in this image resolves only t… - Verification findings (not changed): non-`/local` prefixes are passed through verbatim to the bac… - Test counts: `go test -count=1 ./...` → root package `ok ... 3.007s`; 11 test funcs pass (`Test_g… **End-to-end verification (tier1_real)** - Plain HTTP: built `/tmp/proxy_plain2` from the example; ran a local backend + proxy; `curl http:/… - Balancer: 10 requests via `1284` all `200`; debug log shows strict alternation `addr = 127.0.0.1:… - HTTPS backend: `curl -k https://127.0.0.1:8080/foo` → `bar: 200, 127.0.0.1:...` (backend binary r… - WS: ws server + ws proxy + ws client → 5 echoed timestamps (`recv:` messages through the proxy), … **Final state** - Installed Go 1.24.5 (home dir), dependencies resolved, whole repo builds, `go vet ./...` clean, f…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 15 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fasthttp-reverse-proxy)Questions
- Does fasthttp-reverse-proxy run?
- Yes. fasthttp-reverse-proxy runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test fasthttp-reverse-proxy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3b0dcb225a9f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test fasthttp-reverse-proxy?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fasthttp-reverse-proxy take to install?
- 15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does fasthttp-reverse-proxy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fasthttp-reverse-proxy?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for fasthttp-reverse-proxy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.