Difference between revisions of "Zimbra Proxy Manual:Adding Additional Reverse Proxy To Zimbra Proxy"

m
m
Line 8: Line 8:
  
 
----
 
----
 +
 +
# Introduction #
  
 
Zimbra Proxy is based on nginx. The configuration of reverse proxies is done in templates files.
 
Zimbra Proxy is based on nginx. The configuration of reverse proxies is done in templates files.
  
Example configuration
+
# Example configuration #
Assuming you Zimbra server is reached at https://mail.example.com and you wish to add ownCloud in the same domain
 
https://mail.example.com/owncloud
 
you edit the following template:
 
  
nano /opt/zimbra/conf/nginx/templates/nginx.conf.web.https.default.template
+
Assuming you Zimbra server is reached at https://mail.example.com and you wish to add ownCloud in the same domain ,  https://mail.example.com/owncloud , you edit the following template:
 +
 
 +
nano /opt/zimbra/conf/nginx/templates/nginx.conf.web.https.default.template
  
 
add to the bottom of the file, before the final }
 
add to the bottom of the file, before the final }
Line 24: Line 25:
 
   }
 
   }
  
Then as zimbra user:  zmproxyctl restart
+
Then as zimbra user:
 +
 
 +
  zmproxyctl restart
  
 
This will add the ownCloud in the same domain as your Zimbra server. This can be useful to avoid JavaScript cross-domain issues or for HTTP Authentication pass-thru.
 
This will add the ownCloud in the same domain as your Zimbra server. This can be useful to avoid JavaScript cross-domain issues or for HTTP Authentication pass-thru.

Revision as of 21:47, 7 June 2016

Adding additional reverse proxy to Zimbra Proxy

   KB 22713        Last updated on 2016-06-7  




0.00
(0 votes)

  1. Introduction #

Zimbra Proxy is based on nginx. The configuration of reverse proxies is done in templates files.

  1. Example configuration #

Assuming you Zimbra server is reached at https://mail.example.com and you wish to add ownCloud in the same domain , https://mail.example.com/owncloud , you edit the following template:

nano /opt/zimbra/conf/nginx/templates/nginx.conf.web.https.default.template

add to the bottom of the file, before the final }

  location /owncloud/ {
     proxy_pass https://owncloudserver.example.com/owncloud/;
  }

Then as zimbra user:

zmproxyctl restart
This will add the ownCloud in the same domain as your Zimbra server. This can be useful to avoid JavaScript cross-domain issues or for HTTP Authentication pass-thru.
Jump to: navigation, search