示例
axum 0.8.9: Protect axum routes with stateful middleware using from_fn_with_state, isolate route_layer from 404 fallbacks, and manage bottom-to-top layer execution order
已验证示例 — cargo axum 0.8.9: Protect axum routes with stateful middleware using from_fn_with_state, isolate route_layer from 404 fallbacks, and manage…
sha256:0add9e86ea54fb151285ed7fff0ac6a073835d84159f6bfc43b6e447f030a7be
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
rust linux x64 rust rust cargo
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| rust 1 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-16 |
| rust 1 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-18 |
案例
HOW- 目标
- Protect axum routes with stateful middleware using from_fn_with_state, isolate route_layer from 404 fallbacks, and manage bottom-to-top layer execution order
- 符号
-
- axum::middleware::from_fn
- axum::middleware::from_fn_with_state
- axum::middleware::Next
- axum::Router::route_layer
- axum::Router::layer
- axum::extract::Extension
- axum::extract::State
- axum::extract::Request
- 环境
- rust
- 创建时间
- 2026-08-16T08:11:01Z
契约
- assert route_layer protects routes registered before it, returning 200 with typed Extension and injected headers when authorization token is valid
- assert route_layer rejects unauthorized requests with 401 and custom error headers without invoking the route handler
- assert route_layer leaves public routes registered after it unprotected, returning 200 without executing the auth middleware or incrementing state call counter
- assert an unmatched 404 route on a route_layer router returns 404 Not Found without invoking auth middleware
- assert Router::layer wraps the entire router including 404 fallbacks, returning 401 Unauthorized for unmatched paths when authorization is absent
- assert an unpopulated Extension extractor fails dynamically at runtime with 500 Internal Server Error when the route is not wrapped by the populating middleware
- assert chained layers execute in reverse registration order (bottom-to-top): outer layer runs before inner layer on request, and inner layer runs before outer layer on response
- assert sub-router route_layer middleware is isolated to the nested prefix and does not run on parent router routes
文件
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs
- tests/middleware_tests.rs