-
fix(gateway): a wildcard route no longer swallows explicitly routed subdomains
Release / version (push) Canceled after 0sRelease / frontend (push) Canceled after 0sRelease / linux (amd64) (push) Canceled after 0sRelease / linux (arm64) (push) Canceled after 0sRelease / windows (push) Canceled after 0sRelease / macos (push) Canceled after 0sRelease / release (push) Canceled after 0sBuild and Push Docker Image / build-and-push (push) Canceled after 0sLastSkywalker released this
2026-10-03 21:35:54 +03:00 | 52 commits to main since this release*.example.com passthrough took downloads.example.com away from its own
HTTPS route: on :443 the wildcard is a TCP router, and Traefik applies TCP
routers before any HTTP router on the entrypoint whatever their priority;
on :80 the longer HostRegexp rule outranked Host(), and the passthrough's
ACME router sent the explicit route's challenges to the other proxy.
Explicit hostnames that are direct subdomains of a wildcard are now carved
out of all three wildcard rules (!HostSNI / !Host); the importer skips
negated matchers so they don't return as aliases.Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01NvzfeA1V4Faj7FC5qM5b9qDownloads