I would like to confirm one thing as I debug my code. This code basically takes information from docker and pushes reverse proxy routes to caddy via the API. A replacement for Traefik of sorts
I see that some routes I want to push (via /load
) are different from the respective current ones in caddy (which I get via /config
). This is OK - the route which is pushed is the correct one.
Specifically, the IP address in one of the handles is different in both cases:
"handle": [
{
"handler": "reverse_proxy",
"upstreams": [
{
"dial": "172.18.0.4:9200" â this is different between /load and /config
}
]
}
],
Despite this difference, caddy logs
{"level":"info","ts":1589383873.8353689,"logger":"admin.api","msg":"config is unchanged"}
which obviously is troubling. (not only it logs but the config indeed stays unchanged)
My question: how is the change computed? Or more specifically: should a change in a dial
field trigger a reload of caddy?