How to disambiguate header matcher from header directive

Help
1

Hi, i don’t have any problems. I just have been reading caddy’s documentation and I just have these two confusions yet:
1- Do matcher directives must use a named matcher?
2- It seems header is both a directive and a matcher, how do we disambiguate between matching a header and setting a header?

Any guidance is greatly appreciated. TYIA

2

This is just my personal view, and I could be wrong.

It depends, but generally, no.

In the Caddyfile, a matcher tokenimmediately following the directive can limit that directive’s scope. The matcher token can be one of these forms:

  1. * to match all requests (wildcard; default).
  2. /path start with a forward slash to match a request path.
  3. @name to specify a named matcher.

Good question. When header is part of a named matcher definition line or block, it’s a matcher. When it’s used outside of a matcher definition, it’s a directive.

2 Likes
3

The only acceptable non-named matchers is path, which the wildcard is a special case of. The only similarity between the header matcher and header directive is the name. Their code is different and separate.

2 Likes