Sunjay Bhatia

@artiommocrenco Hey there, have you had a chance to take a look at the discussion above and do you have any thoughts on how you expect things to work? Contour's...

@mmalecki let us know if you would like to have this issue assigned, we would definitely take a PR

@mmalecki what was the path you are matching on for the route(s) you are testing? The [Envoy config field](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-field-config-route-v3-redirectaction-prefix-rewrite) we end up using will replace whatever is matched with the...

This seems to be how the Gateway API words it as well: ``` This type of modifier indicates that any prefix path matches will be replaced by the substitution value....

Here's also an example of path matching/rewriting in practice: https://github.com/projectcontour/contour/blob/main/test/e2e/httpproxy/path_rewrite_test.go Could add an example for the generic match case as well

@mmalecki contour v1.21 is coming up, just checking in if you are still working on this and need anything from us?

I think we might want to add some validation here since the `AppProtocol` field could be a wide range of values and we assume internally that protocol really only is...

We may want to reconsider whether we want to do this at all since this provision Gateway API GEP implies that `appProtocol` is a pretty broad field that Gateway API...

sounds like this could also be done via degraded endpoint load balancing: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/degraded

> Crashing contour is a non starter, so logging is about the best I can think to do at the moment. Hopefully logging at error level will give us a...