Comparing apples to oranges

[p8]

The default filter for https://www.http-arena.com shows Flagship and Emerging frameworks.

The newly added mq-bridge framework is marked as Emerging.
mq-bridge generates and caches response for the first request for the static calls.
Subsequent request return these cached responses.

Comparing frameworks that cache responses to frameworks that generate responses for each request doesn't seem fair.
A casual visitor won't know the difference between Flagship and Emerging and draw incorrect conclusions.

[MDA2AV]

Flagship, Emerging and Experimental all share the same test requirements, the difference between them is maturity. The source of the issue here is a long living problem with Tuned rules for the static files test: https://www.http-arena.com/#doc=test-profiles/h1/isolated/static/implementation

This is HttpArena's fault that allows tuned entries to do this, mq-bridge should be marked as Tuned though. I haven't been too strict on this test because I am currently reworking it and adding validation tests that simulate the files being modified at runtime, invalidating all the current entries that cache files data at startup. I agree this is an inconsistency though, thanks for reporting.

[p8]

Another one is Robyn, it's marked as emerging but caches the pipeline responses:

HttpArena/frameworks/robyn/app.py

Line 45 in bdcb557

@app.get("/pipeline", const=True) # Const route (cached in Rust for max performance)

[MDA2AV]

#930 adds extra validation for static files tests.

rage and rails failing it btw, it assumes a 30 second grace period waiting for the framework to refresh the contents