Chris Ross

@anton-roos are you on .NET 6?

@anton-roos I can't repro this with YARP 1.1.1, the %2F's pass through fine with your given config. Are you sure the issue isn't at your destination servers? Do you have...

See ActivityTimeout: https://microsoft.github.io/reverse-proxy/articles/http-client-config.html#httprequest, https://microsoft.github.io/reverse-proxy/articles/config-files.html

ReassignProxyRequest does set the cluster on the proxy feature, but the ForwarderMiddleware has some references to the original cluster via the route. The fields it's referencing are on the ClusterState,...

Your best option right now is to do the DNS lookup before IHttpForwarder and put the IP directly in the destination url. That way you can manually round robin between...

*edit* that's not HTTP/2 specific, it also helps for HTTP/1.x.

See https://github.com/microsoft/reverse-proxy/blob/main/src/ReverseProxy/Management/IProxyStateLookup.cs

No, transforms aren't applied to routes, they're applied to outgoing requests on a per-request basis. Why would you include transformed routes in the public swagger?

@psavoldelli I'd expect a YARP swagger generator to only cover the routes? The clusters should be opaque to the caller. You can outline a design proposal here, or send a...

We've found that setting the proxy route's Order property to a high value (1000) avoids these kinds of conflicts for routes with wildcards. https://microsoft.github.io/reverse-proxy/articles/config-files.html#all-config-properties