How to read the data of request body and response body in middleware #3159

silent-rain · 2025-01-08T07:53:44Z

silent-rain
Jan 8, 2025

Summary

How to read the data of request body and response body in middleware

Are there any examples available for reference at present? Or could you please provide guidance on how to handle it? thank

impl<S, ReqBody, ResBody> Service<Request<ReqBody>> for DemoService<S>
where
    S: Service<Request<ReqBody>, Response = axum::http::Response<ResBody>> + Clone + Send + 'static,
    S::Future: Send + 'static,
    S::Error: Send + Sync + std::error::Error + Into<BoxError>,
    ReqBody: Send + 'static,
    ResBody: HttpBody<Data = Bytes> + Send + 'static + From<Body>,
    ResBody::Error: Into<BoxError>,
{
    type Response = S::Response;
    type Error = S::Error;
    type Future = BoxFuture<'static, Result<Self::Response, Self::Error>>;

    fn poll_ready(&mut self, cx: &mut std::task::Context<'_>) -> Poll<Result<(), Self::Error>> {
        self.inner.poll_ready(cx)
    }

    fn call(&mut self, req: Request<ReqBody>) -> Self::Future {
        let not_ready_inner = self.inner.clone();
        let mut inner = std::mem::replace(&mut self.inner, not_ready_inner);

        Box::pin(async move {
            let (parts, req_body) = req.into_parts();

            let req_body_bytes = /* How to read data from req_body?  */;
            error!("req body bytes: {:#?}", req_body_bytes);
       
            // If from 'Body:: Creating from (bytes) 'may result in type mismatch, how should I handle it?
           //  If the generic 'ReqBody' is not used, it will conflict with the definition of 'RequestBodyLimitLayer' or third-party definitions
            let req = Request::from_parts(parts, req_body /* req_body has already been consumed */);

            let fut = inner.call(req).await?;
            let (parts, resp_body) = fut.into_parts();

            let resp_body_bytes = /* How to read data from resp_body?  */;
            error!("resp body bytes: {:#?}", resp_body_bytes);

            let res =
                axum::response::Response::from_parts(parts, Body::from(request_body_bytes).into());

            Ok(resp)
        })
    }
}

axum version

axum = "0.8"

mladedav · 2025-01-08T10:38:57Z

mladedav
Jan 8, 2025
Collaborator

That depends on ReqBody and ResBody. Since you want to use this with axum, you should be able to use axum::body::Body for both instead of generics.

1 reply

silent-rain Jan 8, 2025
Author

impl<S> Service<Request> for TimeoutService<S>
where
    S: Service<Request> + Clone + Send + 'static,
    S::Future: Send + 'static,
    S::Error: Into<BoxError>,
    S::Response: Into<Response<Body>>,
{
    type Response = Response<Body>;
    type Error = S::Error;
    type Future = BoxFuture<'static, Result<Self::Response, Self::Error>>;

    fn poll_ready(&mut self, cx: &mut std::task::Context<'_>) -> Poll<Result<(), Self::Error>> {
        self.inner.poll_ready(cx)
    }

    fn call(&mut self, mut req: Request) -> Self::Future {
        let not_ready_inner = self.inner.clone();
        let mut inner = std::mem::replace(&mut self.inner, not_ready_inner);

        Box::pin(async move {
            // ...

            let resp = inner.call(req).await?.into();
            Ok(resp)
        })
    }
}

This example can be satisfied, but when used with 'RequestBodyLimitLayer', an error will be reported，

Or perhaps this approach imposes some limitations on third-party custom middleware ('Commask<Limited>'?), or it could be due to my incorrect usage.

error[E0277]: the trait bound `TimeoutService<PropagateRequestId<Route>>: Service<axum::http::Request<Limited<Body>>>` is not satisfied
   --> admin/src/router.rs:121:10
    |
121 |         .layer(layers)
    |          ^^^^^ the trait `Service<axum::http::Request<Limited<Body>>>` is not implemented for `TimeoutService<PropagateRequestId<Route>>`
    |
    = help: the trait `Service<axum::http::Request<Limited<Body>>>` is not implemented for `TimeoutService<PropagateRequestId<Route>>`
            but trait `Service<axum::http::Request<Body>>` is implemented for it
    = help: for that trait implementation, expected `Body`, found `Limited<Body>`
    = note: required for `CasbinAuthService<TimeoutService<PropagateRequestId<Route>>>` to implement `Service<axum::http::Request<Limited<Body>>>`
    = note: 3 redundant requirements hidden
    = note: required for `Trace<DefaultBodyLimitService<RequestBodyLimit<...>>, ...>` to implement `Service<axum::http::Request<Body>>`
    = note: the full name for the type has been written to '/home/one/Documents/code/RustProject/axum-admin-web/apps/target/x86_64-unknown-linux-gnu/debug/deps/admin-842da95543c3cd3f.long-type-9628096237037994564.txt'
    = note: consider using `--verbose` to print the full type name to the console

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

How to read the data of request body and response body in middleware #3159

{{title}}

Replies: 1 comment 1 reply

{{title}}

{{title}}

Select a reply

How to read the data of request body and response body in middleware #3159

silent-rain Jan 8, 2025

Summary

How to read the data of request body and response body in middleware

axum version

Replies: 1 comment · 1 reply

mladedav Jan 8, 2025 Collaborator

silent-rain Jan 8, 2025 Author

silent-rain
Jan 8, 2025

Replies: 1 comment 1 reply

mladedav
Jan 8, 2025
Collaborator

silent-rain Jan 8, 2025
Author