Chris Ross

Similar request: https://github.com/microsoft/reverse-proxy/issues/1868 Workaround: - That refusal route can be defined in code and sent to an endpoint that produces a 404.

Another ask: https://github.com/microsoft/reverse-proxy/discussions/1928 - Via config, add a response header to all requests that don't match a route. A low priority wildcard route could do this.

That should work with YARP if you follow the instructions here: https://learn.microsoft.com/en-us/aspnet/core/grpc/grpcweb?view=aspnetcore-7.0#configure-grpc-web-in-aspnet-core Be sure to include the DefaultEnabled = true setting. cc: @JamesNK If this does work then we should...

Yes, Grpc.AspNetCore.Web could perform the gRPC-web-to-gRPC translation in the YARP process, and then YARP could proxy the request as gRPC to the destination. For the service registry, see the different...

499 is a non-standard code that NGinx made up. It being a defacto standard might be sufficient cause to use it though. In general, you should look at the ForwarderError...

We're starting to use 499 in AspNetCore for this situation as well: https://github.com/dotnet/aspnetcore/pull/46330 If that goes through then we should do something similar here. We'll even be able to use...

I'd certainly collaborate with you on this. Are you mirroring the whole request/response, or just the bodies? See https://github.com/microsoft/reverse-proxy/issues/105. The bodies are the difficult part. Step 1: A middleware that...

Can you give examples of the config validations you'd like to add? Transforms for example have extensibility built into the validator.

Validating metadata makes sense, that's one of the only fields not already checked by the validator.

This is for outgoing requests from the proxy? YARP uses HttpClient to make outbound requests. HttpClient has two ways of controlling the SNI. The first is the host name from...