Cutlery/caddy
1
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-08-11 09:16:26 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Correct usage of 'comprise'

Kurt 2019-07-02 20:15:33 -04:00
parent e8853fa396
commit 38d2e3dda5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
v2:-Documentation.md

@ -73,8 +73,8 @@ HTTP App
Routes are not your traditional notion of routes (i.e. "GET /foo/bar" -> someFunc).
Routes in Caddy 2 are much more powerful. They are given in an ordered list, and each
route has three parts: match, apply, respond. All parts are optional. Match is the "if"
statement of each route. Each route takes a list of matcher sets. A matcher set is
comprised of matchers of various types. A matcher may be comprised of multiple values.
statement of each route. Each route takes a list of matcher sets. A matcher set
comprises matchers of various types. A matcher may comprise multiple values.
The boolean logic of request matching goes like this:
- Matcher sets are OR'ed (first matching matcher set is sufficient)
@ -629,4 +629,4 @@ performance over a cluster of load-balanced instances, since TLS sessions can al
resumed no matter the load balancing.
FIN.
FIN.