Request Context

RequestContext contains the request method, path, correlation identifiers, headers, bearer token helper, and typed extensions.

#![allow(unused)]
fn main() {
let method = ctx.method();
let path = ctx.path();
let request_id = ctx.request_id();
let trace_id = ctx.trace_id();
let token = ctx.bearer_token();
}

Header lookup is case-insensitive. Caelix lowercases header names when the context is created. An incoming X-Request-Id is retained when valid; otherwise Caelix generates a UUID. trace_id() reads the W3C traceparent trace ID, then X-Trace-Id, and finally falls back to the request ID. Generated controller responses include both identifiers as response headers.

bearer_token() reads the Authorization header and strips the exact Bearer prefix:

Authorization: Bearer eyJhbGciOi...

Guards and interceptors can attach typed values:

#![allow(unused)]
fn main() {
#[derive(Clone)]
pub struct CurrentUser {
    pub id: i64,
}

ctx.set(CurrentUser { id: 42 })?;
}

Typed values are stored by concrete Rust type. A later ctx.set::<CurrentUser>(...) replaces the earlier value for that type.

Guards and interceptors can read values back:

#![allow(unused)]
fn main() {
if let Some(user) = ctx.get::<CurrentUser>()? {
    tracing::info!("user {}", user.id);
}
}

Controllers can read a typed value with #[user]:

#![allow(unused)]
fn main() {
#[get("/me")]
pub async fn me(&self, #[user] user: CurrentUser) -> Result<String> {
    Ok(user.id.to_string())
}
}

If the typed value is missing, the generated wrapper returns 401 Unauthorized with message Not authenticated.

#[user] clones the value out of the context, so user types must be cloneable when used this way.

Cookies

Incoming cookies are available with ctx.cookie("session"). Parsing, controller extraction, response cookies, and session security boundaries are documented in Cookies and Sessions.