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
> Am 26.10.2018 um 08:48 schrieb Edwardo Garcia :
>
> 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)
Why not just use HSTS?
You want separate VirtualHost blocks anyway because you have to decide
where your cert/chain/key files are going to be served so you don't send
SSL traffic over port 80. The SSL engine is enabled at the virtualhost
block level. HSTS is more professional too.
What I do
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
