I'm glad to see Microsoft supporting more low-level magic like this. I've written my own version of ReverseProxyMiddleware more times than I can recall... The most painful parts were always around translating between HttpClient and HttpContext. Looks like Microsoft abstracted this exact concern away under the IHttpForwarder and ForwarderHttpClientContext types.

Looking at the docs around this, I'd probably start w/ Direct Forwarding so I have more control over how things route:

https://microsoft.github.io/reverse-proxy/articles/direct-fo...