Validation

The validation script (scripts/validate.sh) runs these checks for the json-tls test profile. All must pass for a framework to be considered valid for this benchmark.

Checks

ALPN negotiates HTTP/1.1

curl -sk --http1.1 https://localhost:8081/json/1?m=1

The response must report http_version = 1.1. A framework that advertises only h2 on port 8081, or that refuses HTTP/1.1 clients, fails this check.

Response body is correct for multiple (count, m) pairs

Three requests are sent over HTTPS on port 8081 with different counts and multipliers:

For each response the validator checks:

1. count field equals the route count
2. Every item in items has a total field
3. total == price * quantity * m for every item (integer, exact)

These (count, m) pairs are deliberately different from the json-comp validation pairs so a framework that tries to cache validation results across profiles can’t pass both.

Content-Type is application/json

curl -sk -D- -o /dev/null https://localhost:8081/json/1?m=1

The response must include a Content-Type header containing application/json.

Running locally

./scripts/validate.sh <framework>

Filter to this profile only:

./scripts/validate.sh <framework> json-tls