Redirects in Caddy: Safer Patterns for HTTPS, Host and Path Changes

Keep Caddy rules explicit

Caddy is convenient, but redirect logic should still be predictable. Combine host normalization, HTTPS enforcement, and path changes carefully instead of stacking overlapping shortcuts.

Where teams get into trouble

The common mistakes are duplicated host rules, mixing rewrites with redirects, and sending too many cases to the homepage instead of a real replacement URL.

Safer approach

Model the intended destination first, then write the smallest rule set that achieves it. After every change, test protocol, host, trailing slash, and legacy paths as a group.