Is it able to build a parse header only gateway using hyper?

[Dennis-Zhang-SH]

Hi, I am a newbie to rust and hyper, is it able that I only parse the header part of the request, and validate the request then forward it?

[seanmonstar]

Based on your short description, it sounds like yes. The gateway example does that.

[Dennis-Zhang-SH]

Based on your short description, it sounds like yes. The gateway example does that.

Hi, I just checked gateway example, I am assuming that req in service_fn is a completely parsed request? Actually what I want is parsing the header at first, get the authentication token in the header, check if it's valid, if so keep parsing and forward the request, If not stop parsing and return with 401 error.

[seanmonstar]

hyper parses the request headers, the body is not read yet. The body type is a handle to let you stream the body when you want.

[Dennis-Zhang-SH]

hyper parses the request headers, the body is not read yet. The body type is a handle to let you stream the body when you want.

Hi, I tried the gateway example, but it turns out under concurrent pressure, the result is not looking good.

At port 3000, it's just simple axum example code:

Here is part of log:

Listening on http://127.0.0.1:3001
Proxying on http://127.0.0.1:3000
Failed to servce connection: hyper::Error(IncompleteMessage)
Failed to servce connection: hyper::Error(IncompleteMessage)
Failed to servce connection: hyper::Error(IncompleteMessage)
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(IncompleteMessage)
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })
Failed to servce connection: hyper::Error(Shutdown, Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" })

While using other simple proxy like caddy, the result looks much better:

Would you mind explaining why this happened?