thac0/gmnisrv
1
0
Fork 0
forked from aniani/gmnisrv
Code Pull Requests Activity

gmnisrv.ini(5): clarify tokens in route config

Browse Source
This commit is contained in:
Drew DeVault 2020-11-01 10:34:41 -05:00
parent 16e55c6262
commit 953039e0b1
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/gmnisrvini.scd
View File

@ -49,16 +49,16 @@ name of the configuration section is used to determine what kinds of requests it
configures. configures.
The format of the section name is the _hostname_ to be serviced, followed by a 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 token which defines the routing strategy, and a _string_ whose format is
to each routing strategy. The token and match string may be omitted specific to each routing strategy. The token and match string may be omitted
(i.e. [_hostname_] alone), which implies path routing against "/". (i.e. [_hostname_] alone), which implies path routing against "/".
|] *:* |] *:*
:< Route by path prefix. The URL path is compared to "_string_/". :< 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. expression which is tested against the URL path.
See ECMAScript 2018 (ECMA-282, 9th Edition), section 21.2 for a definition of See ECMAScript 2018 (ECMA-282, 9th Edition), section 21.2 for a definition of