Note |
---|
As your Apache is redirecting the requests, it should be able to resolve the domain (DNS lookup) for the CHILI server internally. |
...
Note | ||
---|---|---|
| ||
Make sure that you have the |
HTTPS
When using HTTPS, the httpd-vhost.conf
configuration for your VirtualHost will look slightly different than it would for HTTP
...
Note | ||
---|---|---|
| ||
Apart from the |
CHILI publish Online (SaaS)
When working with SaaS the above vhost files will cause issues because in the above examples the server is setup with an alias of CHILI, but not CHILI publish Online, there is no alias. What you need to do instead is proxy from your subdirectory to the top directory of your CHILI publish Online URL.
Here is an example where we proxy to path editor
Code Block | ||
---|---|---|
| ||
<VirtualHost *:443>
ServerName example.com
ServerAlias www.example.com
DocumentRoot "C:\Php"
<Directory "C:\Php">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require all granted
</Directory>
SSLCertificateFile "C:\wamp64\bin\apache\apache2.4.39\bin\privateCertificate.crt"
SSLCertificateKeyFile "C:\wamp64\bin\apache\apache2.4.39\bin\privateFree.key"
SSLEngine on
SSLProxyEngine on
ProxyPass /editor/ https://myenvironment.chili-publish.online/
ProxyPassReverse /editor/ https://myenvironment.chili-publish.online/
</VirtualHost> |
So, now if I want to get to CHILI BackOffice, I would now go to: https://www.example.com/editor/myenvironment/interface.aspx