Post

Extras you say? * More endpoints, like /echo (echoes back raw HTTP), /encoding/zstd, and /error/reset * Websocket support * Faster & more reliable than either * Combining HTTP & TLS tests (give me an expired cert, then a 404 response) * Chainable endpoints, for both HTTP & TLS

Faster & more reliable? 1. Horizontal autoscaling & globally distributed: low latency everywhere, failover, easy to scale. 2. Cert issuance 100% automated, with ACME and a local CA (many badssl cases need manual setup, and so rot: failing due to expiry, not the real cause).

End result: on my local machine & wifi, curl -kv expired.badssl.com/ takes more than a second, and httpbin.org/anything takes 2.2s. expired.testserver.host/anything takes about 150ms 🚀

httpbin.orghttpbin.org

30/6/26, 11:16 am0 reposts0 likes

testserver.hosttestserver.host

Chainable endpoints? HTTP: testserver.host/info/123/delay/1/status/404 - return a 123 intermediate status, wait 1 second, then return a 404 TLS: incomplete-chain--expired--http2.testserver.host: give me an expired cert, missing the intermediate cert in the chain, and exclusively negotiate HTTP/2.

revoked.testserver.hostrevoked.testserver.host

And combine them too! revoked--tls-v1-2.testserver.host/ws/message/hello/message/goodbye/close A websocket server that only supports TLS v1.2 and uses a revoked certificate - once you connect, it sends hello, then sends goodbye, then closes the connection.

http2.testserver.hosthttp2.testserver.hostGET /echo HTTP/1.1User-Agent: facebookplatform/1.0 (+http://developers.facebook.com)Accept-Encoding: identityAccept: */*Sentry-Trace: 07d6d9eb3f194845ae1c7a388a325401-597a1cc9bba94fd0Baggage: sentry-trace_id=07d6d9eb3f194845ae1c7a388a325401,sentry-sample_rand=0.694727,sentry-environment=production,sentry-release=b2607d563ea96b97afa74ec39e30840bb12e6e73,sentry-public_key=b2dd86967d3344d3bb083da197fca59fHost: http2.testserver.host

Ever wonder what HTTP/1 and HTTP/2 data looks like for the exact same request? http1.testserver.host/echo http2.testserver.host/echo HTTP/1 is a raw string, HTTP/2 includes parsed JSON per frame, with the raw data in the `payload_hex` field.