Module capture
Available on crate features
std and ua only.Expand description
Typed observations of client traffic, before counting or inference.
Protocol captures retain ordered fields and capture completeness. Request-owned
values are represented by bindings rather than reusable literals. A
JointCapture preserves components observed together; ProfileCapture
attaches client, flow and connection identity before ingestion.
Capturing a component does not imply that a replay provider can reproduce it.
Modules§
- completeness
- Source completeness is explicit before an observation becomes profile data.
- headers
- Capture-safe header values and protocol-owned request bindings.
- http2
- Bounded H2 settings and early frames, captured before semantic collapse.
- http3
- HTTP/3 client stream/control prefixes and QPACK instruction shapes.
- joint
- Complete component tuples retain observed cross-component correlations.
- observation
- Resolve profile, flow and component ownership before a counting transaction.
- order
- Protocol-owned order normalization precedes statistical classification.
- pseudo_
headers - Request pseudo-header ordering without retained request values.
- quic
- runtime
- Counted runtime metadata uses the existing typed Web API/source model.
- tls
tls - Capture-safe TLS observations derived from the existing parsed ClientHello.