app.MapDynamicControllerRoute<Router>("{**path}") doesn't seem to affect routing

Question

Edit:

The problem was that app.UseRouting(); was called before app.Use(async (context, next) => {...}). Once I place everything in this order, it worked:

app.Use(async (context, next) { ... });
app.UseRouting();
app.MapControllers();

Original Post:

I'm running a .net 8.0 asp.net minimal API app that is being deployed in various locations, each with different preceding request URL. For instance my search controller:

[ApiController]
[Route("[controller]")]
public class SearchController : ControllerBase {
    [HttpGet] public async Task<ActionResult<SomeValue[]>> Search([FromQuery] string query) { ... }
}

Can be triggered with any of these exemplary strings:

/search?query=term
/api/search?query=term
/some/multi/part/prefix/search?query=term

I tried to find a way to consider only the last part, like [Route([*/controller])], but there's no way to accomplish it using the Route attribute, unfortunately.

So I tried to do some dynamic request manipulations, such as:

app.Use(async (context, next) => {
    context.Request.Path = "/search";
    var request = context.Request.Path.Value;
    var i = request.LastIndexOf('/');
    context.Request.Path = request[..i];
    await next();
});

But albeit witnessing the context.Request.Path indeed changing, the routing itself didn't seem to be affected by it.

So I tried app.MapDynamicControllerRoute<Router>("{**path}") and forced (for the sake of testing):

public class Router : DynamicRouteValueTransformer {
    public override ValueTask<RouteValueDictionary> TransformAsync(HttpContext httpContext, RouteValueDictionary values) {
        httpContext.Request.Path = "/search";
        values["path"] = "search";
        return new(values);
    }
}

And again: httpContext.Request.Path and values["path"] did both reflect the change, but the actual routing hasn't changed, and the controller hasn't been hit.

So what am I missing? any way to accomplish this dynamic routing?

I found no exact match for my case with actual working solution, and couldn't make app.MapDynamicControllerRoute<Router>("{**path}") change actual routing.

Can you please provide a full minimal reproducible example to play with? — Guru Stron
– Guru Stron, Commented Aug 22, 2024 at 22:58
"I'm running a .net 8.0 asp.net minimal API " - also it should be noted that minimal APIs do not use controllers. — Guru Stron
– Guru Stron, Commented Aug 22, 2024 at 22:59

Jerry Fu · Accepted Answer · 2024-08-23 07:23:25Z

0

You could try explicit add app.UseRouting(); after the middleware.

var app = builder.Build();
app.Use(async (context, next) => {
   //if the path contains "search", then change it all to "search"
    if (context.Request.Path.Value.Contains("/search"))
    {
        context.Request.Path = "/search";
    } 
    await next();
});
app.UseRouting();
...

From my experience, if you don't use "app.useRouting()" . Asp.net core will automatically use it at the beginning of middleware pipeline. But when you manually use it, you are forcing a pipeline order to use it.

edited Aug 23, 2024 at 7:23

answered Aug 23, 2024 at 7:13

Jerry Fu

9,7481 gold badge7 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

app.MapDynamicControllerRoute<Router>("{**path}") doesn't seem to affect routing

Edit:

Original Post:

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

Edit:

Original Post:

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related