code
code
cc @blake-snyder Hi, per our offline discussion, I think the final conclusion is keep only one header and only to support on format first, but will add a short prefix...
And I have to say sorry, this is not a big job, but finally it taken your very long time. But I actually don't want to compromise on this point....
Thanks so much for this great contribution and all your patience.
This requirement looks good to me and the jwt_authn filter, gcp_authn filter, RemoteDataSource, etc. have provided similar API. But I think my question would be should we add the `retry_policy`...
We can comment the current situation clearly and do the retry support for other positions in future PR on required
> I don't think retry policy is a property of a URI but of a service. So you could potentially add it to the recently added `envoy.config.core.v3.HttpService`. But in this...
Now we have no an actual API deprecation mechanism. Even a API is marked as deprecated, Envoy need to support them forever. So, it 's hard to replace the HttpUri...