Struct RejectContext 

#[non_exhaustive]
pub struct RejectContext<'a> {
    pub rejection: &'a TokenRejection,
    pub status: StatusCode,
    pub request: &'a Parts,
}

Available on crate feature tower only.

What an on_reject callback (HttpAuthLayerBuilder::on_reject, or the axum layer’s AuthLayerBuilder::on_reject) is told about a refusal.

#[non_exhaustive]: read its fields; more may be added without a breaking change.

Its Debug prints the rejection, the status, the method, the URI’s path (any query as ?***: a client may send an RFC 6750 §2.3 access_token there) and version, and the request’s header NAMES — never a header value, so tracing::warn!(?cx, "refused") cannot log the presented credential (which, for an insufficient-scope refusal, is a validly signed, unexpired token).

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

rejection: &'a TokenRejection

Why the request was refused. TokenRejection::Invalid’s reason is for logs only — never put it in the response.

status: StatusCode

The status the response will carry (401, or 403 for insufficient scope), whatever the callback sets.

request: &'a Parts

The refused request’s method, URI, version, headers and extensions — for content negotiation (Accept), or a per-path error shape.

Trait Implementations

impl Debug for RejectContext<'_>

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.