rust-rpxy

A simple and ultrafast http reverse proxy serving multiple domain names and terminating TLS for http/1.1, 2 and 3, written in Rust

Runssource: GitHubhomepageRustMITcommit cc7a654a845b

Rust, MIT licensed. The project labels itself: acme, http, http proxy, http11, http2, http3, https and load balancing.

rust-rpxy runs. An Argusic agent installed it in 30 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

rpxy 0.14.0 builds from source, all 465 unit tests pass, the binary serves as an HTTP reverse proxy returning 200 from both plaintext local backends and TLS remote upstreams, and TLS termination on port 8443 initializes.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.27 (measured)
recorded runs
2
last tested
stars
792
forks
69
open issues
17
watchers
8
size
3 MB
created
last push

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.

Time lost to each failure while testing rust-rpxy, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Rust not installed in container2 minutes
  • Git submodules not initialized1 minute
Install time
30 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
cargo test: 465 passed (98+5+15+343+4) across 9 suites, exit 0; cargo run --bin rpxy -- --version printed 'rpxy 0.14.0'; curl -H 'Host: test.example.com' via proxy to plaintext backend returned 200 'Hello World!'; curl via proxy to TLS example.com upstream returned 200
Model tokens used
441,941
Exact commit tested
cc7a654a845b
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.

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
Let me compute the total: 98 + 5 + 15 + 343 + 4 = 465 tests passed.
Now let me also verify the binary version one more time.
exec
/bin/sh -lc '. "$HOME/.cargo/env" && cd /work/repo && target/debug/rpxy --version 2>&1 | tail -1' i…
 succeeded in 0ms:
rpxy 0.14.0
All done. Here's my final report:
tokens used
441,941
All done. Here's my final report:

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.
  • Recovered from all 2 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 30 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 acme projects Argusic has installed and timed, rust-rpxy was the 4th fastest to reach a running state, and 4 of 4 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.27
Argusic Runner1/3Runs100.000.08

Topics (from GitHub)

acmehttphttp-proxyhttp11http2http3httpsload-balancingmultidomainpqcproxyreverse-proxyrusttlstls-alpn-01tls-termination

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/rust-rpxy.svg)](https://argusic.com/subject/rust-rpxy)

Questions

Does rust-rpxy run?
Yes. rust-rpxy runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test rust-rpxy?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit cc7a654a845b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test rust-rpxy?
The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does rust-rpxy take to install?
30 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 rust-rpxy need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing rust-rpxy?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does rust-rpxy compare with the alternatives?
Of the 4 acme projects Argusic has installed and timed, rust-rpxy was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
Where is the evidence for rust-rpxy?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion