diff options
| author |  Tobias Schmidt <tobidt@gmail.com>
| 2018-01-30 22:10:07 +0100 |
|---|---|---|
| committer |  Miek Gieben <miek@miek.nl>
| 2018-01-30 23:10:07 +0200 |
| commit | 64d7268ed6760b4a8724182418a700ae2192be85 (patch) | |
| tree | 09c132a88c08cff4c694b6c8f4bc0000610bb8e3 /test | |
| parent | 841e1a44ac15d944962d704780400f75d5945813 (diff) | |
| download | coredns-64d7268ed6760b4a8724182418a700ae2192be85.tar.gz coredns-64d7268ed6760b4a8724182418a700ae2192be85.tar.zst coredns-64d7268ed6760b4a8724182418a700ae2192be85.zip | |
plugin/proxy: Don't enable HTTP healthchecking if not configured (#1441)
HTTP healthchecking will be implicitely activated for proxy upstream
hosts, even if not configured. The README states that not using the
health_check directive will disable HTTP healthchecks though.
It seems to me that the availability of the HealthCheck.Path attribute
is used as indicator whether HTTP healthchecks should be used or not.
The normalizeCheckURL() function didn't check that attribute though,
always returning a CheckURL. This would increase the healthcheck failure
on every third failure in plugin/proxy, without any possibility for the
upstream host to be marked as healthy again. This would eventually
remove all upstream hosts from the serving pool.
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions