From 953039e0b15df9c119b70eb18f36e580a4c4e7d4 Mon Sep 17 00:00:00 2001 From: Drew DeVault Date: Sun, 1 Nov 2020 10:34:41 -0500 Subject: [PATCH] gmnisrv.ini(5): clarify tokens in route config --- doc/gmnisrvini.scd | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/gmnisrvini.scd b/doc/gmnisrvini.scd index 00fbce3..5b936e5 100644 --- a/doc/gmnisrvini.scd +++ b/doc/gmnisrvini.scd @@ -49,16 +49,16 @@ name of the configuration section is used to determine what kinds of requests it configures. The format of the section name is the _hostname_ to be serviced, followed by a -token which defines the routing strategy, and a string whose format is specific -to each routing strategy. The token and match string may be omitted +token which defines the routing strategy, and a _string_ whose format is +specific to each routing strategy. The token and match string may be omitted (i.e. [_hostname_] alone), which implies path routing against "/". |] *:* :< Route by path prefix. The URL path is compared to "_string_/". | *=* -: Exact match. The URL path must exactly match the string. +: Exact match. The URL path must exactly match the _string_. | *~* -: Regular expression routing. The string is a JavaScript-compatible regular +: Regular expression routing. The _string_ is a JavaScript-compatible regular expression which is tested against the URL path. See ECMAScript 2018 (ECMA-282, 9th Edition), section 21.2 for a definition of