Sunjay Bhatia

to clarify, we have a few hops here: 1. client request -> Envoy (which may have the `x-company-role` header) 2. Envoy auth request -> auth server 3. Auth server response...

the tricky thing here is even though it is a totally new feature, i think the crossed out bits in comment https://github.com/projectcontour/contour/pull/4424#issuecomment-1101785837 still does stand, since you could update contour...

moving to 1.22

I think this issue should be augmented (or another created) to add testing for HTTPRoute Filters per-BackendRef as well, since the existing tests only test per-RouteRule Part of that will...

I don't think this is being investigated any longer, removing the label and closing since there hasn't been recent activity

I think the first action item here is to just document for posterity and so we have a sort of decision record what the impact of changing these settings is...

Sorry for the lack of responses on this one @wilsonwu will try to look at this again soon!

@wilsonwu sorry this is so late but when doing the experiment above, did you use a static stat prefix for all routes associated with a virtualhost or do something similar...

per the ongoing discussion on the related PR, looks like this will slip to 1.27.0

We have stalled a bit on working on the ACK/NACK problem because as you say, we've found that we pretty much validate all user input anyways so we don't send...