search

solo-io / gloo

The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
https://docs.solo.io/
Apache License 2.0
4.08k stars 438 forks source link

Support header matching to span multiple routes at gateway or VS top level #8591

Open jameshbarton opened 1 year ago

jameshbarton commented 1 year ago

Gloo Edge Product

Enterprise

Gloo Edge Version

v1.14.15

Is your feature request related to a problem? Please describe.

An Edge Enterprise user is adopting Cloudflare and wants to use this secret-header technique to identify to Gloo Edge that a request is coming from Cloudflare, and should thus be accepted by the Edge route.

This requires a header match to be applied on a per-route basis. It would be more efficient UX to support header matching that spans multiple routes at the gateway or VS top level

Describe the solution you'd like

Support header matching that spans multiple routes at the gateway or top level of a VirtualService.

Describe alternatives you've considered

The workaround is to add a header match condition on each route. It would be more efficient to add it globally.

Additional Context

No response

github-actions[bot] commented 4 months ago

This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.