You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When defining a header in the active health checker, placeholders as header values do not get interpreted altogether.
Expected behaviour
Placeholders set in active health checker headers should be interpreted normally as everywhere else in the Caddyfile.
Steps of bug reproduction
Set a new web server for request catching. This can either be a Caddy server, or any new web server spun up with any language.
Example Caddyfile snippet and WingBlade (JavaScript) web server snippet below.
I guess we didn't enable placeholders there because most placeholders are only available in the context of an HTTP request, which active health checks aren't. But the system and env var placeholders are always available, so that'd make sense.
After 2.7.3 I can add support for this. But not before 😅
Version
Caddy: 2.7.2
Bug description
When defining a header in the active health checker, placeholders as header values do not get interpreted altogether.
Expected behaviour
Placeholders set in active health checker headers should be interpreted normally as everywhere else in the Caddyfile.
Steps of bug reproduction
Example Caddyfile snippet and WingBlade (JavaScript) web server snippet below.
http://127.0.0.1:8081 { log { level INFO } handle /api/example { respond "OK" } }
The text was updated successfully, but these errors were encountered: