rucho
A fast, reliable HTTP echo server and request inspector. Point a gateway at it, send anything, and see exactly what arrived — headers, body, client IP, negotiated TLS, timing.
A fast, reliable HTTP echo server and request inspector. Point a gateway at it, send anything, and see exactly what arrived — headers, body, client IP, negotiated TLS, timing.
No signup, no key, no application to register. It answers immediately:
curl https://rucho.org/get
Ask it for a specific status, a slow response, or a redirect chain — whatever stimulus you need the gateway to react to:
curl https://rucho.org/status/503 # any status code you name
curl https://rucho.org/delay/3 # 3s before the first byte
curl https://rucho.org/redirect/5 # a 5-hop 302 chain
curl "https://rucho.org/response-headers?x-trace=abc" # headers you choose
Everything lives behind Kong on rucho.org, and the same image runs locally:
docker run -p 8080:8080 rumpus/rucho:1.6.0
Thirty-seven endpoints, grouped by the thing you're trying to test.
Echo the request back: method, headers, body, client IP, negotiated TLS.
Make the upstream emit a specific status, header set, redirect chain, or latency.
Non-JSON bodies — XML, HTML, images, decoded base64, byte ranges.
Already-encoded bodies (gzip/deflate/brotli) regardless of Accept-Encoding.
Revalidation, cache directives, and chunked drip-feed responses.
Inspect, set, and expire cookies.
Health, metrics, and the runtime endpoint list.
Generators: random bytes and UUIDs.
Every endpoint, with parameters and response shapes. The console sends real requests.