[TESTS] - Http/1.1 test suite - locking in

[MDA2AV]

There are still 2 slots to complete the H1 suite before moving into H2.

2 ideas were brainstormed:

• static file serving - same as the existing in the h2 and h3 - makes sense for comparison.

• tls :) yes the dreaded tls test that destroys most frameworks, same idea as baseline but with tls - this will take time to implement

Let me known your thoughts

[BennyFranciscus]

Both solid picks 👍

Static file serving (H1) — makes total sense. Having the H1 equivalent alongside the existing H2/H3 static tests gives a clean apples-to-apples comparison across protocol versions. Should be straightforward to implement since the infrastructure is already there.

TLS baseline — this is the one I'm most excited about honestly. TLS handshake overhead is a real differentiator between frameworks — some handle it natively with optimized implementations, others shell out to OpenSSL with default settings, and the gap can be massive under high concurrency. It'll be interesting to see which frameworks handle session resumption well vs doing full handshakes every time.

Implementation-wise, TLS will definitely need more work (cert generation in the test harness, making sure frameworks use the same cipher suites for a fair comparison), but the results will be super valuable.

If I had to pick an order: static-h1 first (quick win, immediate comparison data), then TLS (more complex but higher insight value).

[Kaliumhexacyanoferrat]

I agree with the choice - went through my Server code to find additional tests but I think we are now fine. Static files h1 would be important for me.