https://bz.apache.org/bugzilla/show_bug.cgi?id=64996
Rich Bowen <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #6 from Rich Bowen <[email protected]> ---
So, after a deep dive into how vhost matching actually works in practice,
rewrote the "Virtual Host Matching" section with a clearer two-phase structure
and an explicit priority table:
Phase 1 (connection time) — IP address and port matching priority:
1. Exact IP, exact port
2. Exact IP, wildcard port
3. Wildcard IP (*), exact port
4. Wildcard IP, wildcard port
5. Main server
Phase 2 (per request) — Name-based matching among vhosts that tied
at the same priority level:
1. Match ServerName/ServerAlias against Host header (first wins)
2. Fall back to first listed vhost (default name-based vhost)
Key clarification: once a match is found at a given priority level,
lower-priority levels are never considered — even if a lower-priority
vhost has a matching ServerName. This was the core source of confusion.
Also documents: SSL/SNI handling, ServerPath legacy fallback,
persistent connection behavior, and absolute URI handling.
Patched in r1933669 (trunk), r1933670 (2.4).
*Phew* Had this in draft for a while, and finally getting it polished a little.
:)
Thanks for the detailed analysis, Christoph — your breakdown of the
matching algorithm in comment #2 was particularly helpful.
--
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.