Skip to main content

YARP–Direct forwarding in .NET 6 and beyond

With YARP(Yet-Another-Reverse-Proxy) you can transform your ASP.NET Core application into a reverse proxy.

It offers features like routing, discovery, load balancing, retries,... However in the application I'm building that is a lot more then what I need. I only need the ability to take a specific request and forward it to a specific destination. In that case you can use Direct Forwarding through the IHttpForwarder.

IHttpForwarder supports:

  • Dynamic destination selection, you specify the destination for each request
  • Http client customization, you provide the HttpMessageInvoker
  • Request and response customization (except bodies)
  • Streaming protocols like gRPC and WebSockets
  • Error handling

It does not include:

  • Routing
  • Load balancing
  • Affinity
  • Retries

Direct forwarding in .NET 6 and beyond

You can find an example of Direct Forwarding in the documentation. However this documentation is written for .NET 5 still using the Startup.cs class.

Let me share an example on how to achieve the same thing in .NET 6:

You can find the complete example here:

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should