Struct RUser 

pub struct RUser {
    pub id: String,
    pub token: String,
}

Authenticated User Information | 已认证用户信息

RUser is the core concept of r-token. It implements actix-web’s FromRequest trait, enabling “parameter-as-authentication” by using it directly as a handler parameter.

RUser 是 r-token 最核心的概念，它实现了 actix-web 的 FromRequest trait， 可以作为 Handler 的参数直接使用，实现“参数即鉴权“的效果。

How It Works | 工作原理

When you declare RUser as a handler parameter, actix-web automatically:

当你在 Handler 参数中声明 RUser 时，actix-web 会自动：

1. Extracts the Token from the Authorization header | 从请求的 Authorization header 中提取 Token
2. Validates the Token through RTokenManager | 通过 RTokenManager 验证 Token 的有效性
3. If valid, creates an RUser instance and passes it to your handler | 如果验证通过，创建 RUser 实例并传递给你的 Handler
4. If invalid, returns 401 Unauthorized without calling the handler | 如果验证失败，直接返回 401 Unauthorized，Handler 不会被调用

Zero-Intrusion Design | 零侵入式设计

You don’t need any if/else checks in your business code to verify if a user is logged in. If a parameter has RUser, the user is guaranteed to be authenticated!

你不需要在业务代码中写任何 if/else 来检查用户是否登录， 只要参数里有 RUser，就保证用户一定是已登录的！

Example | 示例

use actix_web::{get, HttpResponse};
use r_token::RUser;

#[get("/protected")]
async fn protected_route(user: RUser) -> impl actix_web::Responder {
    // If we get here, user is guaranteed to be valid! | 能进到这里，user 一定是合法的！
    HttpResponse::Ok().body(format!("Welcome, user {}", user.id))
}

Fields

id: String

User ID | 用户 ID

Corresponds to the user identifier passed during login | 对应登录时传入的用户标识符

token: String

User’s Token | 用户的 Token

The Token string extracted from the Authorization header | 从 Authorization header 中提取的 Token 字符串

Trait Implementations

impl Debug for RUser

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

Formats the value using the given formatter.

impl FromRequest for RUser

FromRequest Trait Implementation | FromRequest trait 实现

This is the key to r-token’s “parameter-as-authentication” feature.

这是 r-token 实现“参数即鉴权“的关键。

Execution Flow | 执行流程

When actix-web receives a request and finds a handler needs an RUser parameter, it automatically executes this logic:

当 actix-web 收到请求并发现 Handler 需要 RUser 参数时，会自动执行这里的逻辑：

1. Get Token Manager | 获取 Token 管理器: Extract RTokenManager from app_data | 从 app_data 中提取 RTokenManager
2. Extract Token | 提取 Token: Get Token from Authorization header (supports Bearer prefix) | 从 Authorization header 中获取 Token（支持 Bearer 前缀）
3. Validate Token | 验证 Token: Check if Token exists in manager’s storage | 检查 Token 是否存在于管理器的存储中
4. Return Result | 返回结果:
   • Success → Create RUser instance, handler executes normally | 成功 → 创建 RUser 实例，Handler 正常执行
   • Failure → Return 401 Unauthorized, handler is not called | 失败 → 返回 401 Unauthorized，Handler 不会被调用

Error Handling | 错误处理

• 500 Internal Server Error: Token manager not injected into app_data | Token 管理器未注入到 app_data
• 401 Unauthorized: Token missing or invalid | Token 缺失或无效

type Error = Error

The associated error which can be returned.

type Future = Ready<Result<RUser, <RUser as FromRequest>::Error>>

Future that resolves to a Self.

fn from_request(req: &HttpRequest, _payload: &mut Payload) -> Self::Future

Create a Self from request parts asynchronously.

fn extract(req: &HttpRequest) -> Self::Future

Create a Self from request head asynchronously.