See dotnet/aspnetcore#46818

AspNetCore 8.0 adds a new middleware for applying request timeouts. This augments HttpContext.RequestAborted. Timeouts can be configured globally, per endpoint, and/or by policy.

Problem 1) global timeouts can negatively impact long-running requests like WebSockets, gRPC, SignalR, etc.. Since YARP manages its own timeouts it should consider disabling the global default when proxying.

Problem 2) should YARP allow specifying timeout policies per registered route, similar to CORS, Auth, etc..? Or is that redundant with YARP's timeout settings?