From f26e250648f11528ed5d3191d3ebc0ebd7278308 Mon Sep 17 00:00:00 2001 From: Aofei Sheng Date: Thu, 16 Feb 2023 22:54:05 +0800 Subject: [PATCH] Mention PathPrefix matcher changes in V3 Migration Guide --- docs/content/migration/v2-to-v3.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/content/migration/v2-to-v3.md b/docs/content/migration/v2-to-v3.md index 3a9c7e4c4..b52fa6703 100644 --- a/docs/content/migration/v2-to-v3.md +++ b/docs/content/migration/v2-to-v3.md @@ -35,11 +35,13 @@ In v3, the reported status code for gRPC requests is now the value of the `Grpc- In v3, the `Headers` and `HeadersRegexp` matchers have been renamed to `Header` and `HeaderRegexp` respectively. +`PathPrefix` no longer uses regular expressions to match path prefixes. + `QueryRegexp` has been introduced to match query values using a regular expression. `HeaderRegexp`, `HostRegexp`, `PathRegexp`, `QueryRegexp`, and `HostSNIRegexp` matchers now uses the [Go regexp syntax](https://golang.org/pkg/regexp/syntax/). -All matchers now take a single value (except `Headers`, `HeaderRegexp`, `Query`, and `QueryRegexp` which take two) +All matchers now take a single value (except `Header`, `HeaderRegexp`, `Query`, and `QueryRegexp` which take two) and should be explicitly combined using logical operators to mimic previous behavior. `Query` can take a single value to match is the query value that has no value (e.g. `/search?mobile`).