Files
coredns/middleware.cfg
Miek Gieben 26242cef1b Document fallthrough and fix rewrite (#537)
* Document fallthrough and fix *reverse*

While documenting the fallthrough behavior and testing it I noticed
the did not properly work. This PR does a tiny bit too much as it

- Documents fallthrough
- Fixes fallthrough in reverse
- Makes directives_generate complain on duplicate priorities
- Moved reverse *before* file in middleware.cfg
- Add a test that tests the reverse fallthrough behavior with a file
  backend

Fixes #515

* ....and fix the tests
2017-02-20 21:00:00 +00:00

44 lines
1.0 KiB
INI

# Directives are registered in the order they should be
# executed.
#
# Ordering is VERY important. Every middleware will
# feel the effects of all other middleware below
# (after) them during a request, but they must not
# care what middleware above them are doing.
# How to rebuild with updated middleware configurations:
# Modify the list below and run `go gen && go build`
# The parser takes the input format of
# <order>:<middleware-name>:<package-name>
# Or
# <order>:<middleware-name>:<fully-qualified-package-name>
#
# External middleware example:
# 80:log:github.com/miekg/coredns/middleware/log
# Local middleware example:
# 80:log:log
10:root:root
20:bind:bind
30:trace:trace
40:health:health
50:pprof:pprof
60:prometheus:metrics
70:errors:errors
80:log:log
90:chaos:chaos
100:cache:cache
110:rewrite:rewrite
120:loadbalance:loadbalance
130:dnssec:dnssec
140:reverse:reverse
150:file:file
160:auto:auto
170:secondary:secondary
180:etcd:etcd
190:kubernetes:kubernetes
200:proxy:proxy
210:whoami:whoami
220:erratic:erratic