Deploy with a Reverse Proxy - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services
Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

Follow this guidance if you want to run Content Service with a reverse proxy.

If the reverse proxy maps the target server to a different context path, or if you deployed specifically to a different context path, you need to follow the steps in Deploy with a Different Context Path, with the following changes:
  1. In step 2, update the values in the alfresco-global.properties file: 
     alfresco.context=xxx
 alfresco.host=xxx
 alfresco.port=xxx
 alfresco.protocol=xxx

    where xxx are the externally visible context, host name, port number and protocol values.

  2. You must specify the context path that’s externally visible in all steps, and not the context path that the repository is actually running on. Exceptions are in:
    • Step 1 and step 3 - if Share is connecting to the repository directly and not through the reverse proxy.
    • Step 7 - if Solr is contacted directly and not through the reverse proxy.