ProxyKit VS YARP

Worth noting that YARP (or as someone has eloquently described it as PRAY) here was another Microsoft project which basically killed a previous open source project which did the same thing:

https://github.com/proxykit/ProxyKit

This actually feels like one of the instances that PeachPie with a combination of ProxyKit or YARP would be handy.

You could setup a proxy with ProxyKit in you WebHost. Your blazor app will send requests to, say http://webhost:5000/api/endpoint. The host will then forward the request to http://webapi:3000/endpoint (or whatever). You'll have to setup some kind of JWT authentication where the WebHost generates a JWT on login and saves it in the cookie. Good thing here is, the cookie really only contains some id the server uses to look up the actual contents of the cookie. Only the cookie gets returned to the browser (blazor app). On each api request, the webhost will fetch the token out of the server-side cookie and append it to the Authorization header. The webapi will validate the token and return the response that will be proxied back to your front-end.

Adding to the other answers here, you might find some useful functionality in YARP if you want a pure .NET reverse proxy. Like Kestrel, Microsoft dogfoods YARP in Azure.

➡️ Release 2.0.0-RC.1 · microsoft/reverse-proxy · GitHub ➡️ Visual Studio 2022 17.5 Preview 3 is here!

In your application, you may be using YARP, to build a reverse proxy gateway sitting in front of various backend applications. For example, you may run YARP to listen on example.org, and have it proxy all requests going to this domain while mapping /api and /docs to different web apps running on diffreent servers.

Microsoft already made YARP for their Azure infrastructure, it's a "build your own reverse proxy" kit.

If I was to need one I would probably reach for YARP (Yet Another Reverse Proxy) from MS. https://microsoft.github.io/reverse-proxy/

Microsoft's YARP is exactly this.