Josh Knapp
2ef582a3de
All checks were successful
HAProxy Manager Build and Push / Build-and-Push (push) Successful in 56s
Adds a new env var HAPROXY_SUSPENSION_BACKEND (default unset). When set (e.g. "whp-suspended:80"), generate_config() renders: - A bk_suspended backend pointing at the configured upstream - An ACL `acl is_suspended_domain hdr(host),lower -f /etc/haproxy/suspended_domains.list` + `use_backend bk_suspended if is_suspended_domain` in the frontend, sitting after IP-blocking and before any per-domain routing - An empty /etc/haproxy/suspended_domains.list if missing (haproxy refuses to start with -f pointing at a non-existent file) External tooling (e.g. WHP's site_disable.php) maintains the list via `docker cp` and HUP-reloads the container. Non-WHP deployments (home networks, standalone use) leave the env var unset and see byte-identical haproxy.cfg output. Same opt-in shape as the existing HAPROXY_CORAZA_SPOE_BACKEND integration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
14 lines
664 B
Smarty
14 lines
664 B
Smarty
# Suspended-site backend. Used when external tooling adds a host to
|
|
# /etc/haproxy/suspended_domains.list (read by an ACL in the frontend).
|
|
# The backend points at a single upstream that serves a static 503
|
|
# "site temporarily unavailable" page. Only rendered when the
|
|
# HAPROXY_SUSPENSION_BACKEND env var is set on the haproxy-manager
|
|
# container; non-WHP deployments (home networks, standalone use) see
|
|
# no change to haproxy.cfg.
|
|
backend bk_suspended
|
|
mode http
|
|
option http-server-close
|
|
http-request set-header X-Forwarded-Proto https if { ssl_fc }
|
|
http-request set-header X-Forwarded-For %[src]
|
|
server suspended {{ target }} check inter 30s
|