I can post my configuration, but I don’t think that this is like it is intended to be.
Basically I simply created a new file at /etc/httpd/conf.d that must have the ending .conf.
The content of that file is:
<VirtualHost *:80>
ServerName subdomain.domain.com
ProxyPreserveHost On
ProxyPass / http://10.10.0.10/
ProxyPassReverse / http://10.10.0.10/
</VirtualHost>
<VirtualHost *:443>
ServerName subdomain.domain.com
ProxyPreserveHost On
SSLEngine On
SSLProxyEngine Off
SSLCertificateFile /etc/httpd/conf.d/subdomain.domain.com.pem
SSLCertificateKeyFile /etc/httpd/conf.d/subdomain.domain.com.key
SSLCertificateChainFile /etc/httpd/conf.d/intermediate_cl1_ca.pem
SSLCACertificateFile /etc/httpd/conf.d/root_ca.pem
ProxyPass / http://10.10.0.10/
ProxyPassReverse / http://10.10.0.10/
</VirtualHost>
But I am ignoring the Template-Stuff of Nethserver doing this.
Port 80:
The configuration redirects every request to Nethserver that is to the domain subdomain.domain.com to my server 10.10.0.10 and passes also the HTTP-Header.
Port 443:
If a query to subdomain.domain.com is to the Nethserver, it will forward the HTTPS-Request as an HTTP-Request to my Webserver 10.10.0.10. The HTTP-Answer will be “converted” to an HTTPS-Answer by the ReverseProxy (=Nethserver) and send back to the Client.
The infrastructure for this scenario is
Client => HTTPS => Nethserver => HTTP => Webserver
So the Webserver don’t need to be configured to do something with HTTPS (except you are using Tomcat in some cases as I figured out). You need valid SSL-Certificates for the HTTPS stuff.
Thats how I did it.
PS:
You can repeat the config above for each (sub)domain you have. Just change the “ServerName”-Parameter. The first config that matches your Parameters will be processed by the build in Apache in Nethserver.
PPS:
After you updated the .conf-File you have to execute this command at the console of Nethserver:
signal-event nethserver-httpd-update