footing 0.6.6

Feature-gated foundations for Rust backend services
Documentation
//! Request identifiers, trusted forwarding, and request-scoped context.
//!
//! For a native reqx example that forwards validated correlation identifiers to
//! a fixed downstream service, run:
//!
//! ```text
//! cargo run --example request_correlation --features http
//! ```
//!
//! The example keeps headers on individual requests and exercises two local
//! services. It demonstrates correlation passthrough, without creating spans.
//! Applications using distributed tracing should let their instrumentation
//! establish parent/child spans and inject the active context instead of
//! forwarding the incoming `traceparent` unchanged. See the
//! [OpenTelemetry propagation model](https://opentelemetry.io/docs/concepts/context-propagation/).

mod context;
mod forwarding;
mod identifiers;

pub use context::{
    CLIENT_ID_HEADER_NAME, LOCALE_HEADER_NAME, MAX_REQUEST_CONTEXT_VALUE_LENGTH,
    MAX_USER_AGENT_LENGTH, RequestContext, SESSION_ID_HEADER_NAME, TIME_ZONE_HEADER_NAME,
    UTC_OFFSET_HEADER_NAME,
};
pub use forwarding::{ClientIpSource, ForwardedHeadersStatus};
pub use identifiers::{
    MAX_REQUEST_ID_LENGTH, MAX_TRACEPARENT_LENGTH, REQUEST_ID_HEADER_NAME, RequestId,
    RequestIdError, TRACEPARENT_HEADER_NAME, TRACEPARENT_LENGTH, TraceParent, TraceParentError,
    is_valid_request_id, is_valid_traceparent,
};

#[cfg(test)]
mod tests;