Module http_header_control_pair 

First built-in payload strategy: http.header.control-pair@1.

This strategy derives a matched control/candidate pair for a single benign request header so a strategy-aware capability executor can measure whether a target responds differently to exactly one controlled header change. It is deliberately the lowest-risk built-in strategy: it emits only visible ASCII header-value bytes and can never introduce control characters, so it cannot perform header injection or request splitting.

The strategy operates on a fixed header for this revision. The control leg is a conventional, seed-independent baseline (the “normal profile”); the candidate leg is that baseline plus one controlled, seed-derived variation. Derivation is a pure function of (role, seed) — no clocks, randomness, knowledge state, or transport.

Structs

HttpHeaderControlPairStrategy

First built-in PayloadStrategy: a single-header control/candidate pair.

Constants

HTTP_HEADER_CONTROL_PAIR_HEADER_NAME

Request header this revision varies. A strategy-aware executor applies the derived artifact bytes as the value of this header.

HTTP_HEADER_CONTROL_PAIR_ID

Stable identity of this strategy, without its revision.

HTTP_HEADER_CONTROL_PAIR_REVISION

Deterministic implementation revision materialized by this module.