Chris Ross

This is currently impacted by https://github.com/dotnet/aspnetcore/issues/41692. IProxyHttpClientFactory was renamed to IForwarderHttpClientFactory

See https://microsoft.github.io/reverse-proxy/articles/http-client-config.html#custom-iforwarderhttpclientfactory > For some customizations you can derive from the default [ForwarderHttpClientFactory](https://microsoft.github.io/reverse-proxy/api/Yarp.ReverseProxy.Forwarder.ForwarderHttpClientFactory.html) and override the methods that configure the client. See https://microsoft.github.io/reverse-proxy/api/Yarp.ReverseProxy.Forwarder.ForwarderHttpClientFactory.html#Yarp_ReverseProxy_Forwarder_ForwarderHttpClientFactory_WrapHandler_Yarp_ReverseProxy_Forwarder_ForwarderHttpClientContext_HttpMessageHandler_ Triage: DelegatingHandlers are a common scenario worth...

There may be some functional/conceptual overlap with Degraded health state. https://github.com/microsoft/reverse-proxy/issues/2071

How does the load / RPS compare?

> `HttpContext.Request.Body.Seek(0, SeekOrigin.Begin);` > > Although we haven't yet evaluated the performance impact of doing this, I think it would be helpful to include it as some kind of option...

WebSockets and gRPC won't have significantly different performance characteristics in this streaming scenario.

For path based routing we're limited to what's available in ASP.NET Core Routing. What you can do is use the route parameters to capture the tenant ID and then use...

Correct, this is not currently implemented. x-forwarded is the recommended mechanic but I understand that's not always viable. We recommend x-fowarded because Location is only one of many fields that...

There's a fundamental issue in aspnetcore with %2F and %252F that makes it impossible for YARP to correctly round trip both values (https://github.com/dotnet/aspnetcore/issues/30655). #1219 defaulted to the safer of the...

Implementing INodeBuilderPolicy in HeaderMatcherPolicy is one way we can approach this.