Chris Ross

Nothing specific in the plans yet. AspNetCore already has an in-memory [response cache](https://docs.microsoft.com/en-us/aspnet/core/performance/caching/response?view=aspnetcore-3.1) that should be proxy compatible (it keys off response cache headers). Someone could probably adapt it to...

The response caching middleware linked above caches in-memory. You could certainly fork that to prototype caching to disk. AspNetCore already has FileBufferingWriteStream that would be useful here. https://github.com/dotnet/aspnetcore/blob/47e21d4849cc6cb88fc9ca9c95054add1261e312/src/Http/WebUtilities/src/FileBufferingWriteStream.cs#L20

RE: https://github.com/dotnet/aspnetcore/issues/40229

ForwardedHeadersMiddleware wasn't designed for use in the proxy (YARP), it's designed for use in the backend. You'll get the expected results if you remove that middleware. Is there something you...

Ah, ok. Since YARP is the temporary component here then your best option is probably to use ForwardedHeadersMiddleware, `{"X-Forwarded": "Set"}`, and `{ "RequestHeaderRemove": "X-Original-For" }`. You should end up with...

Please share the full log and stack trace you're concerned about. > Add a configuration flag to toggle the logging of TaskCanceledException since it is an expected exception. We have...

Does TimeoutPolicy work instead? `"TimeoutPolicy": "customPolicy",`

Brainstorming: `dotnet yarp` global tool that runs the single file exe using appsettings.json in the local directory. Compare to `dotnet serve`.

@b0 as an ingress controller (https://github.com/microsoft/reverse-proxy/issues/200) or as a simplified deployment model? Packaging this exe up into a pre-built container would be one step to consider beyond the development of...

@b0 Good to know. We may split containerizing out into a separate issue when we get around to working on the exe scenario.