Ingress Gateway: Wildcard path based routing
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 43
Description
#### Feature Description
Ingress gateways currently support wildcards, however this only works based on the Host/Authority headers of the request.
Path based routing requires a `service-router` which does not support wildcards.
One way to address this issue: https://github.com/hashicorp/consul/issues/9712
Another is to support wildcard path based routing in Ingress Gateways.
#### Use Case(s)
Most legacy applications have configurable URLs, it is almost universally easier to configure them to call:
http://{ingress-gateway-address}:{ingress-gateway-port}/{name-of-service}/path/to/query
Than to call:
-H "Host: {name-of-service}.ingress.consul" http://{ingress-gateway-address}:{ingress-gateway-port}/path/to/query
Contributor guide
Assessment
This issue has not been assessed yet.