These .http files exercise scripting APIs that httpsuite provides but the
JetBrains HTTP Client CLI (ijhttp) does not. They are kept out of the parity
suite in ../tests/ because you cannot test "matches JetBrains" on
an API JetBrains doesn't expose.
Running these through ijhttp fails with ReferenceError: <name> is not defined — that is expected, not a bug. Running them through httpsuite passes.
| File | httpsuite-only API |
|---|---|
04_crypto_hmac.http |
crypto.hmac.* (and, by the same token, crypto.subtle and jwt) |
Verified empirically: against ijhttp (GraalJS engine) crypto is not a defined
global, so these are additive httpsuite features rather than JetBrains-compatible
behaviour. Run them against httpsuite only:
go run ./conformance --dir conformance/extensions --ijhttp ""