diff options
| author | Francis Lavoie <lavofr@gmail.com> | 2021-05-12 18:18:44 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-12 16:18:44 -0600 |
| commit | b82db994f39c6991d673a7ae9836f5454b1f9668 (patch) | |
| tree | 905452da2039e68eea404547f52377a1f5b05fcb /modules/caddyhttp | |
| parent | aef8d4decceba3371d6722a81e17cd5f94162116 (diff) | |
caddyfile: Add parse error on site address with trailing `{` (#4163)
* caddyfile: Add parse error on site address in `{`
This is an incredibly common mistake made by users, so we should catch it earlier in the parser and give a more friendly message. Often it ends up adapting but with mistakes, or erroring out later due to other site addresses being read as directives.
There's not really ever a situation where a lone '{' is valid at the end of a site address (but I suppose there are edgecases where the user wants to use a path matcher where it ends specifically in `{`, but... why?), so this should be fine.
* Update caddyconfig/caddyfile/parse.go
Diffstat (limited to 'modules/caddyhttp')
0 files changed, 0 insertions, 0 deletions