Skip to main content

ASP.NET Core - Branch the ASP.NET Core request pipeline–Map vs MapWhen

Yesterday I blogged about the usage of the MapWhen() method to branch the request pipeline in ASP.NET Core. What I didn’t mention is that in a first attempt I used the Map() method instead of the MapWhen() method.

Map() will branch the request based on the specified request path whereas MapWhen() allows you to specify a predicate giving you more options on what criteria should be used for branching.

Let’s have a second look at the MapWhen() implementation I was using:

You would think I could replace this with the following Map() alternative:

This turns out not to be the case. Apart from the predicate logic, another difference between Map() and MapWhen() is that Map() will add MapMiddleware to the pipeline while MapWhen will add MapWhenMiddleware to the pipeline. An important difference between these 2 middleware is that Map() will update the Request.Path and Request.PathBase to account for branching based on path (trimming the matched path segment off Request.Path and appending it to Request.PathBase).

In the example above, the ServerSideEvents middleware I’ve added to the pipeline will listen to requests on ‘api/bel/api/bel’ what is not what I want. To achieve the expected behavior, I should rewrite the middleware like this:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...