Any other way to get RouteId from inside a middleware?

[goenning]

I found that the RouteId is assigned to context.GetEndpoint.DisplayName and it works fine for my use case, which is to perform some transformation and validation based on that, but it does look brittle at the moment as it could change in upcoming versions. Is there any other way to get access to the RouteId (or even RouteConfig) using the HttpContext? Thanks.

[Tratcher]

What kind of transformations did you have in mind? We've got a whole infrastructure for that.
https://microsoft.github.io/reverse-proxy/articles/transforms.html

Edit: And no, that's the only way to get the route id right now.

[goenning]

we're looking to do request/response body transformation which will vary per route, hence why the custom middleware and why it's important for us to know which route is being proxied for a particular request

[Tratcher]

Makes sense. Do you actually inspect the route id, or do you use that as a key to look up the metadata you need to make this decision? I ask because there's a few different ways that custom information could be appended to a route and exposed to middleware.

E.g. ProxyRoute.Metadata

reverse-proxy/src/ReverseProxy/Abstractions/RouteDiscovery/Contract/ProxyRoute.cs

Line 53 in c81cf0b

public IDictionary<string, string> Metadata { get; set; }

,

Or Endpoint Metadata: #328

[goenning]

Yes, that was my initial plan. I was going to use the RouteId to look up the Metadata from the list of proxy routes, which is what triggered this thread looking for better ways of retrieving the RouteId. Is there any other way to have access to the ProxyRoute.Metadata from a middleware? I saw that RouteConfig is stored in the Endpoint, but unfortunately it's unaccessible. Thanks

[Tratcher]

ProxyRoute.Metadata isn't exposed at the moment, but that does sound like what you'd need here. Can you open something at https://github.com/microsoft/reverse-proxy/issues to track that?

[goenning]

Thanks, just opened this one 👍 #587