This doesn't work correctly in 2.4.x... but needs to be fixed in trunk for 2.next.
The problem is that our connection rec structure defers to the vhost structure for the port assignment, a 1:1 mapping. We need to break this and trust the vhost is 1:many, and the connection rec records which inbound port the request was accepted on. And then tweak everywhere in httpd core modules and encourage third party authors to adopt the new convention. On Fri, Oct 26, 2018 at 1:49 AM Edwardo Garcia <wdgar...@gmail.com> wrote: > Hi, > We have only few domains to manage, usually either http or https, but we > have lately had requests for both (we know defeat purpose but customer > knows what they want and they no take monetary or personal informations on > website) > > I know this works with duplication of virtualhosts, but should it also > work with > <VirtualHost 1.2.3.4:80 [2001:1:1:1::1]:80 1.2.3.4:443 > [2001:1:1:1::1]:443> > ... > </VirtualHost> > To avoid duplicating? > nginx does not seem to have this limitation, so I'm surprised httpd2 does. > > If I omit ports, it will errors on http if ssl engine on. > > or have I overlooked option? > > Willy > >
