Struct TimeoutLayer 

pub struct TimeoutLayer<A: ?Sized> { /* private fields */ }

Available on non-WebAssembly only.

Wraps any owned Application (or a shared Arc<dyn Application>) so every request through it must complete within duration or the client gets 504 Gateway Timeout instead of waiting further.

Use this to put one blanket timeout around an entire App/AppWithState/ custom Application. For different timeouts on different routes within the same app, use with_timeout / with_timeout_state / with_timeout_async on individual handlers instead.

Implementations

impl<A: Application + Send + Sync + 'static> TimeoutLayer<A>

pub fn new(inner: A, duration: Duration) -> Self

Wrap an owned application.

impl<A: Application + Send + Sync + ?Sized + 'static> TimeoutLayer<A>

pub fn from_arc(inner: Arc<A>, duration: Duration) -> Self

Wrap an already-shared application (e.g. Arc<dyn Application + Send + Sync>).

Trait Implementations

impl<A: Application + Send + Sync + ?Sized + 'static> Application for TimeoutLayer<A>

fn execute( &self, request: &Request, connection: &ConnectionInfo, ) -> Result<Response, String>

Receives a parsed request and returns a fully-built response. Walk your controller list with is_matching / process and return the first match.

fn registered_routes(&self) -> Vec<RouteInfo>

The routes this application registers, as (method, pattern) — what AppWithState::route_entries returns; wrappers (WithMiddleware, McpServer) report the routes of the application inside. For tools that describe an app (the dev MCP server’s routes tool), not for dispatch. Default: none. Since 18.28.0.

fn middleware_names(&self) -> Vec<&'static str>

The names of the middleware layers around this application’s routes, in the order a request passes them (Middleware::layer_name). Default: none; WithMiddleware lists its layers, then the inner application’s. Since 18.28.0.

fn runs_inline(&self, _request: &Request, _connection: &ConnectionInfo) -> bool

true when executing request is quick and never waits on anything but the local filesystem — health checks, metrics, small static files. The async servers (HTTP/1.1, HTTP/2, HTTP/3) then call execute directly on the event loop, as nginx does, instead of handing the request to tokio’s blocking pool: that handoff (a shared lock and two cross-thread wake-ups) costs more than serving a small file.

fn execute_async<'a>( &'a self, _request: &'a Request, _connection: &'a ConnectionInfo, ) -> Option<AsyncResponse<'a>>

Available on crate feature http2 only.

An asynchronous version of execute for this request, when the application has one: the async servers await it on the connection’s task instead of tying up a blocking-pool thread while it waits (the config-driven proxy uses this to wait for a backend without holding a thread). None (the default) means “use execute”. Wrappers return Some only when they add no synchronous work of their own.

fn streams_body(&self, _request: &Request, _connection: &ConnectionInfo) -> bool

true to receive this request’s body as a stream (Body::Stream) instead of read into memory first: execute then runs while the body is still arriving, on a blocking-pool thread, and reads it with std::io::Read — a multi-gigabyte upload in a few chunks of memory. Asked after the head is read, so request.body is empty here; decide from the method, path and headers.