iitwelders 2. try

This commit is contained in:
Andreas Knuth 2025-09-11 12:24:15 -05:00
parent d80df95f43
commit 47b5b7e8fd
1 changed files with 11 additions and 18 deletions

View File

@ -102,35 +102,28 @@ gregknoppcpa.bayarea-cc.com {
encode gzip encode gzip
} }
iitwelders.bayarea-cc.com { iitwelders.bayarea-cc.com {
# Optional: Basis-Hardening
encode zstd gzip encode zstd gzip
header {
# Browser-ähnlicher Forward (optional)
-Server
X-Frame-Options "SAMEORIGIN"
}
# Falls die Zielseite nur www. spricht, nimm https://www.iitwelders.com reverse_proxy https://iitwelders.com {
reverse_proxy https://www.iitwelders.com { # Wichtig: als Host explizit die Apex-Domain setzen,
# Very important: Origin-Host durchreichen # damit der Upstream NICHT auf iitwelders.com umleitet.
header_up Host www.iitwelders.com header_up Host iitwelders.com
# Übliche Forwarded-Header
header_up X-Forwarded-Host {host} header_up X-Forwarded-Host {host}
header_up X-Forwarded-Proto {scheme} header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-For {remote_host} header_up X-Forwarded-For {remote_host}
# Manchmal blocken Upstreams komische Encodings von Proxys # TLS SNI passend zum Upstream-Host
header_up Accept-Encoding identity
# SNI/ServerName für TLS Richtung Upstream
transport http { transport http {
tls_server_name www.iitwelders.com tls_server_name iitwelders.com
} }
# Optional: ein "normales" User-Agent setzen, falls der Upstream picky ist # Falls der Upstream Probleme mit komprimierten Requests hat:
header_up User-Agent {>User-Agent} header_up Accept-Encoding identity
} }
# Optional: Healthcheck-Route fürs Monitoring # Optional: einfache Health-Route
@health path /_health @health path /_health
respond @health "ok" 200 respond @health "ok" 200
} }