proksi tested by Argusic Runner

What the test found

Proksi 0.6.1 builds from source, its 38 tests pass, and the launched server proxies HTTPS requests over TLS to a configured upstream returning 200, while its HTTP service answers /ping with 200 and redirects other paths to HTTPS.

Proksi 0.6.1 built with cargo build; 38 tests passed. Server launched serving TLS on 8443 and HTTP on 8080. Real app behavior verified end-to-end: HTTPS routed a real GET over HTTP/2 to a local mock upstream and returned 200; HTTP /ping returned 200 'pong'; other HTTP paths returned 308 redirect to https. The end-to-end proxy request used a local mock upstream I stood up on port 9099; nothing about Proksi itself was mocked.

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

Runsall runs of proksi

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.