DO NOT REPLY [Bug 43218] Wrong cert used for vhost if ServerName is same

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=43218

Bapf <as...@bapf.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |asf@bapf.de
            Version|2.2.4                       |2.2.17
         OS/Version|FreeBSD                     |Linux

--- Comment #4 from Bapf <as...@bapf.de> 2010-10-27 11:19:25 EDT ---
We're having the same bug with apache httpd 2.2.17 on linux and more: We don't
just get a warning, the server refuses to start with this kind of configuration
(which worked fine up until now).

We also found the same workaround as described in comment #1.

While this workaround is working we're having quite a few problems with it:
When using mod_proxy with this workaround the ProxyPassReverse-directive
substitutes the internal hostnames with the external hostname _and_ the port
(as specified in the ServerName-Directive) which causes a lot of hazzle if the
internal host isn't ssl-enabled. (We regularly end up with redirects in the
form of http://ext-hostname:443/path)

I know that this kind of NameBasedVirtualHosting for SSL-Hosts never was
officially supported but a lot of people depend heavily on it.

My question is now: Is the requirement of the port in the ServerName-directive
a bug and can I expect a fix for this or is it working as intended (as part of
the changes necessary for server name indication)?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org