Hardening

Zion applies security defaults that can be overridden via configuration.

Response Headers

Every HTTPS response includes these security headers (stored as static HeaderValue constants):

Header	Value	Purpose
Strict-Transport-Security	max-age=63072000; includeSubDomains; preload	Force HTTPS for 2 years
X-Content-Type-Options	nosniff	Prevent MIME sniffing
X-Frame-Options	DENY	Block iframe embedding
Referrer-Policy	strict-origin-when-cross-origin	Limit referrer leakage
Permissions-Policy	camera=(), microphone=(), geolocation=(), payment=()	Disable browser APIs
Server	(removed)	No server identification

Method Whitelist

Only these HTTP methods are accepted. All others return 405 Method Not Allowed:

GET  POST  PUT  PATCH  DELETE  HEAD  OPTIONS

This blocks TRACE (cross-site tracing), CONNECT (proxy tunneling), and non-standard methods before any processing occurs.

URI Length Limit

Requests with URI paths exceeding 8,192 bytes return 414 URI Too Long.

Header Limits

Hyper is configured with reduced header limits compared to defaults:

Parameter	Zion	Hyper Default
Max header count	64	100
Max header buffer	16 KB	400 KB

Rate Limiting

Per-IP rate limiting using DashMap with atomic counters:

[server]
rate_limit_rps = 100          # Max requests per IP per window
rate_limit_window_secs = 1    # Window duration

When rate_limit_rps = 0 (default), rate limiting is disabled — the code returns before accessing any map. Over-limit requests return 429 Too Many Requests.

Timeouts

Timeout	Duration	Purpose
TLS handshake	10 seconds	Prevent TLS slowloris
HTTP request	60 seconds	Kill stalled connections
Upstream connect	3 seconds (configurable)	Fail fast on dead upstreams
Connection pool idle	30 seconds	Reclaim unused upstream connections

Connection Limit

Maximum concurrent connections are bounded by a Semaphore sized to available RAM:

conn_limit = (RAM_MB / 4) * 1024 / 50    # ~50KB per TLS connection estimate

Clamped to 1,000–100,000. Connections beyond the limit are silently dropped at the TCP level.

HTTP to HTTPS Redirect

Port 80 serves only two purposes:

1. ACME challenges: /.well-known/acme-challenge/* is proxied to the configured upstream
2. Everything else: 301 Moved Permanently redirect to https://

The Host header is validated before use in the redirect URL:

• Must be non-empty and <= 253 characters
• Must not contain /, \, @, newlines, or spaces

Internal-Only Routes

Routes marked with internal_only = true are restricted to private IPs:

127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12,
192.168.0.0/16, 169.254.0.0/16, ::1

External requests receive 403 Forbidden.

Linux-Specific Options

On Linux, Zion enables additional socket options when the kernel supports them:

• TCP_DEFER_ACCEPT: Kernel holds connections until client sends data
• TCP_FASTOPEN: TFO for returning clients (requires kernel support)
• SO_REUSEPORT: Kernel-level connection distribution across listeners

0-RTT Replay Protection

TLS 1.3 0-RTT is enabled but gated by HTTP method. Non-idempotent methods (POST, PUT, PATCH, DELETE) on early data receive 425 Too Early (RFC 8470). Only GET and HEAD are allowed on 0-RTT data.

See TLS Configuration → 0-RTT Replay Protection for details.

Hop-by-Hop Header Stripping

Zion strips the following hop-by-hop headers from upstream responses before forwarding to clients (RFC 7230 §6.1):

Connection, Keep-Alive, Proxy-Authenticate, Proxy-Authorization,
TE, Trailer, Transfer-Encoding, Upgrade

X-Forwarded-For Policy (xff_mode)

Outbound XFF behaviour is configured at [server] level. The default (append) preserves the prior behaviour and is correct when Zion sits behind a sanitising edge (CDN/ALB) that has already vetted the inbound chain. When Zion is the front edge, the default is unsafe: a client can send X-Forwarded-For: 1.2.3.4 and the leftmost entry in the chain forwarded to your upstream will be that attacker-controlled value. Downstream apps that read XFF[0] for ACL or audit will be tricked.

[server]
xff_mode = "rewrite"   # one of: "append" | "rewrite" | "drop"

Mode	Inbound XFF	Outbound XFF	Use when
append (default)	preserved	inbound chain + resolved client IP appended	Zion is behind a trusted edge that already strips/normalises XFF
rewrite	dropped	single entry: the resolved client IP	Zion is the front edge — guarantees a clean one-hop chain regardless of what the client sent
drop	dropped	not emitted	Upstreams must not learn the client IP at all

X-Real-IP is always set from the resolved client IP and never trusted from inbound headers, regardless of xff_mode. The "resolved client IP" is the output of TrustedProxies::resolve_client_ip: the rightmost X-Forwarded-For entry that is not a trusted-proxy CIDR, or the TCP peer IP when no proxies are configured.

mTLS Client Certificate Forwarding

When the TLS listener is configured with client-certificate verification (client_ca_path set, client_auth = "required" or "optional"), Zion extracts a stable identifier from the leaf peer certificate and forwards it to upstreams as:

X-Client-Cert-Fingerprint: sha256:<64 hex chars>

The value is the SHA-256 of the leaf DER, hex-encoded with a sha256: prefix — the same convention used by openssl and nginx ($ssl_client_fingerprint). It is collision-resistant and stable across re-issuance only when the cert bytes themselves are stable; rotating a cert produces a new fingerprint.

Earlier Zion versions emitted X-Client-Cert-DN, computed as a 64-bit XOR-fold of the first 64 DER bytes. That value was advertised as a "DN" but was neither a Distinguished Name nor collision-resistant; it has been removed. If your upstream still expects the old header, map it at the upstream side from X-Client-Cert-Fingerprint (note: the new value is a fingerprint, not a DN, and downstream identity mapping must be done via your roster).

Hot-reload

Zion applies changes to zion.toml and to the certificate files referenced by [tls] without restarting the process. An invalid config is rejected and the previous snapshot keeps serving traffic, so the only way a config edit can break production is if it is a valid config that does the wrong thing.

The full contract — what reloads, what is left to a restart, how to verify a reload landed — is in Operations → Hot-reload.

Content-Security-Policy

Per-route CSP headers can be configured. See Routing → Content-Security-Policy.