https://bz.apache.org/bugzilla/show_bug.cgi?id=64997

            Bug ID: 64997
           Summary: documenation about implictily added ServerAliases from
                    VirtualHost directive names seem incomplete
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Documentation
          Assignee: docs@httpd.apache.org
          Reporter: cales...@scientia.net
  Target Milestone: ---

Hi.

vhosts/name-based.html says:
> The complete list of names in the VirtualHost directive are treated just like 
> a (non wildcard) ServerAlias.

and
vhosts/details.html says:
> The complete list of names in the VirtualHost directive are treated just like 
> a (non wildcard) ServerAlias (but are not overridden by any ServerAlias 
> statement).


1) First, the wording here is a bit strange, especially the "(non wildcard)"...
no sure what that really tries to tell here, as a domainname in VirtualHost
couldn't contain a wildcard anyway?

If it means that *:* or *:80 doesn't implicitly add "*" as a ServerAlias, that
should be made more clear.

But from my testing it rather means that any name where the port is "*", like
"example.com:*" wouldn't get added.




2) Second and more important, the described behaviour seems only half the
truth. From my live tests it seems that a (Server)Alias is only added for
accesses made on the port that is given together with the domainname in
<VirtualHost>.

Consider the following example in that order:
(with foo.example.com pointing to 10.10.10.10 in DNS)

VirtualHost 10.10.10.10:80 10.10.10.10:8080>
        ServerName default-vhost.example.com
        ...
</VirtualHost>

VirtualHost 10.10.10.10:80 10.10.10.10:8080 foo.example.com:80>
        ServerName other-vhost.example.com
        ...
</VirtualHost>

An access to foo.example.com:80 will end up on other-vhost, but(!) an access to
foo.example.com:8080 ends up on default-vhost  ... which is unexpected as
other-vhost also listens on 10.10.10.10:8080 and allegedly the domainname from
it's VirtualHost would have been added as ServerAlias.

But it's apparently not generally added, *but only* for the indicated port.


Cheers,
Chris

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org

Reply via email to