If you really don't need vhost-specific HTTPS configurations (have wildcard
certificate?), you can probably make HTTPS copies of all of your HTTP vhosts
with some clever use of mod_proxy and mod_rewrite. I wouldn't recommend going
this way though, sounds like interesting exercise but more troubl
Hi Daniel,
Thanks for trying to help but maybe I didn't explain this well enough.
Debian uses "Include" by default because of it's built-in `a2ensite`
shortcut.
Even with the Include (as your code illustrates) there needs to be a
Virtual Host configuration block for HTTP on port 80 and for HTTPS
There is a directive called "Include"
With this directive you can specify any number of directives in a file
and then define the Include pointing to the same file wherever you may
need.
For instance
Include conf/common.conf
SSLEngine on
SSLCertificatefile conf/x509.crt
SSLCertitificateKeyFil
Hello,
I am a user of Apache in the sense that I install it, configure it and run
it to host sites...I'm hoping this is the correct list to send this to.
Anyway, I recently did my first "from scratch" Apache install, build and
configuration in a cloud server (I had always used cPanel & WHM before
