Content.Node package configuration

1 Using HTTPS

1.1 Virtual host configuration

To use HTTPS, you must add a corresponding virtual host to the httpd. You can do this by copying the original non-HTTPS-enabled virtual host:


cd /Node/apache/conf/sites-available
cp cms.conf cms_ssl.conf

Then adjust the VirtualHost directive to use the HTTPS port and add the mod_ssl configuration:

/Node/apache/config/sites-available/cms_ssl.conf

<VirtualHost *:443>

SSLEngine on
SSLCertificateFile /Node/apache/conf/ssl/server.crt
SSLCertificateKeyFile /Node/apache/conf/ssl/server.key

SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown

1.2 Apache configuration

Activate the virtual host and mod_ssl:


cd /Node/apache/config/sites-enabled/
ln -s ../sites-available/cms_ssl.conf 010-cms_ssl.conf
cd ../mods_enabled
ln -s ../mods_available/ssl.load

Create the /Node/apache/config/ssl directory and copy your certificate and key files there as mentioned in the virtual host configuration.

If you don’t have a commercial certificate yet and just want to test the HTTPS functionality you can also generate a self-signed certificate.

If you use a commercial certificate, you must provide the complete certificate chain. You can do this by either adding the SSLCACertificatePath directive or by using the SSLCertificateChainFile directive instead of SSLCertificateFile.

1.3 Restart

Finally, restart Content.Node


/Node/bin/nodectl restart