From b952f814c11a206730e719e00760fe5af83b827f Mon Sep 17 00:00:00 2001 From: Ludovic Fernandez Date: Fri, 10 Jun 2022 09:24:08 +0200 Subject: [PATCH] docs: fix rule expression render --- docs/content/routing/routers/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/routing/routers/index.md b/docs/content/routing/routers/index.md index 9b209151e..d22f034df 100644 --- a/docs/content/routing/routers/index.md +++ b/docs/content/routing/routers/index.md @@ -849,7 +849,7 @@ The table below lists all the available matchers: Hence, only TLS routers will be able to specify a domain name with that rule. However, there is one special use case for HostSNI with non-TLS routers: when one wants a non-TLS router that matches all (non-TLS) requests, - one should use the specific `HostSNI(*)` syntax. + one should use the specific ```HostSNI(`*`)``` syntax. !!! info "Combining Matchers Using Operators and Parenthesis"