gpt4 book ai didi

server - 如何从 actix-web 中间件返回早期响应?

转载 作者:行者123 更新时间:2023-11-29 08:31:00 28 4
gpt4 key购买 nike

我的客户通过 Authorization header 中的 token 进行授权,每个请求都需要检查该 header 。如果缺少此 header 或找不到相应的用户,我想返回 HTTP 代码 Unauthorized,否则我想正常处理请求。

目前我有很多重复的代码,因为我在每个请求处理程序中检查这个 header 。actix docs在第一段中建议可以停止请求处理以尽早返回响应。如何实现?

由于我还没有找到实现此行为的示例,所以我尝试提出自己的中间件函数,但它无法编译。

为了克服返回两种不同类型(ServiceResponseMap)的问题,我已经把返回值装箱了,所以问题在How do I conditionally return different types of futures?中提出不是问题。更重要的是,我不知道该 wrap_fn 函数的返回值究竟需要哪些类型和哪些特征实现。我现在拥有的那些不起作用。

App::new()
.wrap(Cors::new().allowed_origin("http://localhost:8080"))
.register_data(state.clone())
.service(
web::scope("/routing")
.wrap_fn(|req, srv| {
let unauth: Box<dyn IntoFuture<Item = ServiceResponse>> = Box::new(ServiceResponse::new(req.into_parts().0, HttpResponse::Unauthorized().finish()));
let auth_header = req.headers().get("Authorization");
match auth_header {
None => unauth,
Some(value) => {
let token = value.to_str().unwrap();
let mut users = state.users.lock().unwrap();
let user_state = users.iter_mut().find(|x| x.auth.token == token);
match user_state {
None => unauth,
Some(user) => {
Box::new(srv.call(req).map(|res| res))
}
}
}
}
})
.route("/closest", web::get().to(routing::find_closest))
.route("/fsp", web::post().to(routing::fsp))
.route("/preference", web::get().to(routing::get_preference))
.route("/preference", web::post().to(routing::set_preference))
.route("/find_preference", web::post().to(routing::find_preference))
.route("/reset", web::post().to(routing::reset_data)),
)
.bind("0.0.0.0:8000")
.expect("Can not bind to port 8000")
.run()
.expect("Could not start sever");

我在编译时遇到了两个错误。

1.

error[E0191]: the value of the associated types `Future` (from the trait `futures::future::IntoFuture`), `Error` (from the trait `futures::future::IntoFuture`) must be specified
--> src/server/mod.rs:36:41
|
36 | let unauth: Box<dyn IntoFuture<Item = ServiceResponse>> =
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| |
| associated type `Future` must be specified
| associated type `Error` must be specified

2.

error[E0277]: the trait bound `dyn futures::future::IntoFuture<Item = actix_web::service::ServiceResponse>: futures::future::Future` is not satisfied
--> src/server/mod.rs:35:22
|
35 | .wrap_fn(|req, srv| {
| ^^^^^^^ the trait `futures::future::Future` is not implemented for `dyn futures::future::IntoFuture<Item = actix_web::service::ServiceResponse>`
|
= note: required because of the requirements on the impl of `futures::future::Future` for `std::boxed::Box<dyn futures::future::IntoFuture<Item = actix_web::service::ServiceResponse>>`

最佳答案

你可以创建自己的类型,Authorized,实现FromRequest为此,将 Authorized 定义为处理程序中应检查授权的参数。

简化示例:

use actix_web::dev::Payload;
use actix_web::error::ErrorUnauthorized;
use actix_web::{web, App, Error, FromRequest, HttpRequest, HttpResponse, HttpServer};

fn main() {
HttpServer::new(move || App::new().route("/", web::to(index)))
.bind("127.0.0.1:3000")
.expect("Can not bind to '127.0.0.1:3000'")
.run()
.unwrap();
}

fn index(_: Authorized) -> HttpResponse {
HttpResponse::Ok().body("authorized")
}

struct Authorized;

impl FromRequest for Authorized {
type Error = Error;
type Future = Result<Self, Error>;
type Config = ();

fn from_request(req: &HttpRequest, _: &mut Payload) -> Self::Future {
if is_authorized(req) {
Ok(Authorized)
} else {
Err(ErrorUnauthorized("not authorized"))?
}
}
}

fn is_authorized(req: &HttpRequest) -> bool {
if let Some(value) = req.headers().get("authorized") {
// actual implementation that checks header here
dbg!(value);
true
} else {
false
}
}

此代码产生:

$ curl localhost:3000
not authorized⏎
$ curl localhost:3000 -H 'Authorized: i am root'
authorized⏎

您可能可以使用中间件以相同的方式做一些事情,但我还没有完全了解中间件抽象。此外,您可能希望向处理程序提供有用的信息,例如用户名:

struct Authorized {
username: String
}

关于server - 如何从 actix-web 中间件返回早期响应?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/57892819/

28 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com