Headers
Response metadata that agrees with itself.
/bytesReturns n random bytes with accurate Content-Length and Content-Type: application/octet-stream. Deterministic by ?seed= for reproducibility. Counterpart to /bytes, which lies about byte count or MIME type.
/cache-confusedReturns a single, sensible Cache-Control directive (`public, max-age=300`). Counterpart to the chaos /cache-confused endpoint, which combines mutually contradictory directives.
/wrong-content-typeReturns a JSON body labelled application/json — the Content-Type matches the body. Counterpart to the chaos /wrong-content-type endpoint, which mismatches the two on purpose.
/rangeReturns correct HTTP Range responses: 206 with the exact requested bytes and an accurate Content-Range header, 416 for unsatisfiable ranges, 200 + full body on If-Range ETag mismatch. Counterpart to /range, which lies about which bytes it returns.
Headers that don’t lie. The Content-Type matches the body; the Cache-Control directive is single and sensible. If your client’s caching/parsing behavior diverges between these and the chaos counterparts, the chaos detection is real.