Skip to content

fix: stop 421 for own hostnames with no route - #667

Merged
savme merged 1 commit into
mainfrom
fix/own-hostname-never-misdirected
Oct 19, 2026
Merged

savme merged 1 commit into
mainfrom
fix/own-hostname-never-misdirected

Conversation

@savme

@savme savme commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

This is a follow-up to #659. The 421 now fires for a hostname with no route on its own connection. The retry would land in the same place and get another 421.

The PR adjusts misdirect handling to account for hostnames with no routes.

Case Main This PR
Hostname with no route, own connection 421 404
Another site's hostname on a reused connection 421 421
Subdomain of a wildcard hostname that another gateway serves 421 421

Test plan

  • Unit tests cover own hostnames, wildcard hostnames, overlapping gateways and listeners without a hostname.
  • Lint passes on the extension server.
  • The misdirected-request e2e scenario passes in the test env.

Related to #661

@savme
savme marked this pull request as ready for review October 19, 2026 14:08
@savme
savme requested a review from a team as a code owner October 19, 2026 14:08
@savme
savme merged commit 7552bb3 into main Oct 19, 2026
18 checks passed
@savme
savme deleted the fix/own-hostname-never-misdirected branch October 19, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants