The custom header does not work properly when it contains Chinese characters about reverse-proxy

[MihaZupan]

You can check debug Kestrel logs from the proxy, but it's very likely that you are running into the fact that non-ASCII header values are not allowed by default, but you can opt-in to using a different encoding (e.g. UTF8) - see the relevant documentation section here.

[a34546]

The configuration of using UTF8 encoding for the request header still yields the same result.
The console also has no error logs.
Please help me check if the configuration is correct.

[MihaZupan]

Have you configured Kestrel to accept the headers as well (ConfigureKestrel sample the docs)?

[a34546]

This is my code.

I'm not sure if there are any missing .
Please help me check.
Thank you

[239573049]

You should have set it up

[MihaZupan]

Can you provide a minimal runnable repro project for this issue and/or a network capture?
Without that, we're just guessing at what the problem might be.

It is odd that the client is seeing the server as unresponsive instead of getting back an error about an invalid request.