Alexander Yastrebov

> This is not consistent, and the filters should be applied to the response in these cases, too. In order to achieve this, we need to create a dummy response...

Regarding https://github.com/zalando/skipper/issues/1238#issuecomment-727915854 we may combine two ideas: convert `Proxy.do()` early return on error into proper error response but pass it to new `ErrorResponse()` optional filter method - this way there...

If I get it right the idea is to use path parameter in the backend hostname. This is possible with a help of [template placeholders](https://github.com/zalando/skipper/blob/master/docs/reference/filters.md#template-placeholders) and a route: ``` PathSubtree("/api/:buildVersion")...

Some thoughts for the context. We could establish some kind of convention to lookup value from the `secrets.SecretsReader` e.g. if client_id/client_secret starts with a prefix like `secret:/opt/ms-client-id`. We would also...

Looks like a duplicate if #901

Related issue #225

> What do you think @AlexanderYastrebov ? I would like to see a compelling usecase. As far as I understand, requests excluded by the proposed predicate will end up getting...

> What's the use case? Match routes with known header value without revealing the actual value to the parties that have access to the routes source (source code, ingress definitions,...

Golang issue https://github.com/golang/go/issues/32204

Regarding > example: oauthTokeninfoCompareHeaderAny("https://idp.example.org/oauth2/tokeninfo", "uid", "X-Uid", "uuid", "X-Uuid", "group", "X-Group") The filter would allow the request to pass if one of the values match: uid from token and X-Uid header...