eli
3c58aec356
Caddy injects runtime auto-redirect routes (host-matched, ahead of the catch-all http:// site, not excluding ACME challenge paths) for domains it manages certs for — invisible in static 'caddy adapt' output, so the previous live test could not reproduce it. hy2's tokens got 308'd to 443 (LE: 'Invalid response from https://DOMAIN/...: 404' via masquerade). Verified bidirectionally with real caddy v2.11.4: without the option the challenge path gets 308 (exact production repro), with it 200 from hy2. Live test now extracts the global block + http block + a tls-internal managed site block to reproduce production conditions permanently. Co-Authored-By: Claude <noreply@anthropic.com>
7 lines
66 B
Plaintext
7 lines
66 B
Plaintext
.codegraph/
|
|
dry-run-output/
|
|
caddy.log
|
|
caddy.pid
|
|
mock.pid
|
|
mock.log
|