As I said in my comment, this is not what has been asked, but as requested I am explaining my configuration.
I am warning everyone that I am not a network administrator, and even if I am using Alfresco on production use (with back up etc...) the website I am running is not under heavy load, or mission critical, and no-body is interested in hacking my website. So the scenario and configuration below may be unsuitable for you.
Scenario:
- Host: one EC2 instance (Linux)
- http blocked by EC2 rule, https only allowed
- Apache listening to https
- Alfresco 4.2 default installation, listening http
And the configuration for my domain:
<VirtualHost *:443>
ServerName mydomain.com
ServerAlias www.mydomain.com
DocumentRoot /alldomain/mydomain/https
ErrorLog path.to.log
SSLEngine on
SSLCertificateFile /path.to.crts/mydomain.crt
SSLCertificateKeyFile /path.to.keys/mydomain.key
SSLCertificateChainFile /path.to.pems/sub.class1.server.sha2.ca.pem
ProxyPass /share ajp://127.0.0.1:8009/share
ProxyPassReverse /share ajp://127.0.0.1:8009/share
ProxyPass /alfresco ajp://127.0.0.1:8009/alfresco
ProxyPassReverse /alfresco ajp://127.0.0.1:8009/alfresco
</VirtualHost>
As I also said I have many advantages:
- Easier to renew and change certificates
- I can redirect users when doing Alfresco maintenance
- I can tune http cache to reduce load on Alfresco