h-duplicate-setting
· RFC 9114 §7.2.4 · discretionary · layer http3 · udp/4476 · MAY
Passing this means: The RFC permits either behaviour; the report says which was chosen.
Anomaly type: control_stream
How each client answered
| Client | Version | Verdict | What happened |
|---|---|---|---|
| curl | ngtcp2/1.11.0 | Pass | Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant. |
| quinn | noq fork | Pass | Rejected with error 0x109. The specification permits this but does not require it; a client that ignored it would also be conformant. |
| aioquic | 1.3.0 | Pass | Rejected with error 0x109. The specification permits this but does not require it; a client that ignored it would also be conformant. |
| chromium | build 1223 | Pass | Rejected with error 0x109. The specification permits this but does not require it; a client that ignored it would also be conformant. |
| quic-go | quic-go v0.61.0 | Pass | Rejected with error 0x106. The specification permits this but does not require it; a client that ignored it would also be conformant. |
| quiche | 0.30.0 | Pass | Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant. |
| neqo | 0.31.1 | Pass | Tolerated it and continued. The specification permits this but does not require it; a client that rejected it would also be conformant. |
What the clause requires
Either reject with H3_SETTINGS_ERROR or ignore the repeat — the specification says a receiver MAY treat this as an error, so both are conformant.
Judged against RFC 9114.
Run this one yourself
Every test is reachable from your own client. Nothing here needs an account.
curl -s https://conformance.pqcrypta.com/catalog.json \
| jq '.tests[] | select(.id == "h-duplicate-setting")'What this suite is · The full grid · All clients · All tests · Findings