From a02694771bfad3a64a401bdda6d7bb2ad9db558b Mon Sep 17 00:00:00 2001 From: Nathan Coleman Date: Fri, 23 Jun 2023 19:22:52 -0400 Subject: [PATCH] docs: add note about path prefix matching behavior for HTTPRoute config (#17862) --- .../gateways/api-gateway/configuration/http-route.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/website/content/docs/connect/gateways/api-gateway/configuration/http-route.mdx b/website/content/docs/connect/gateways/api-gateway/configuration/http-route.mdx index 997e2bbf692e..02d2725ad698 100644 --- a/website/content/docs/connect/gateways/api-gateway/configuration/http-route.mdx +++ b/website/content/docs/connect/gateways/api-gateway/configuration/http-route.mdx @@ -533,6 +533,11 @@ Specifies the HTTP method to match. Specifies type of match for the path: `"exact"`, `"prefix"`, or `"regex"`. +If set to `prefix`, Consul uses simple string matching to identify incoming request prefixes. For example, if the route is configured to match incoming requests to services prefixed with `/dev`, then the gateway would match requests to `/dev-` and `/deviate` and route to the upstream. + +This deviates from the +[Kubernetes Gateway API specification](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2fv1beta1.PathMatchType), which matches on full path elements. In the previous example, _only_ requests to `/dev` or `/dev/` would match. + #### Values - Default: none