Difference between revisions of "Zimbra Proxy Manual:Adding Additional Reverse Proxy To Zimbra Proxy"
m |
|||
| Line 6: | Line 6: | ||
{{WIP}} | {{WIP}} | ||
<div class="col-md-9">{{ZimbraProxyManual}}</div> | <div class="col-md-9">{{ZimbraProxyManual}}</div> | ||
| − | + | </div> | |
---- | ---- | ||
Latest revision as of 20:51, 7 February 2019
Adding additional reverse proxy to Zimbra Proxy
- This article is a Work in Progress, and may be unfinished or missing sections.
| General Proxy Overview | |||
|---|---|---|---|
| Overview And Planning For Zimbra Proxy | Installing , Configuring, Disabling the Zimbra Proxy | Zimbra Proxy Related CLI Commands | Troubleshooting Zimbra Proxy |
| Advanced Topics | |||
|---|---|---|---|
| Configuration And Template Files And Proxy Related Variables | Advanced Proxy Configuration Examples via CLI | Miscellaneous Topics | Zimbra Proxy Manual:Adding Additional Reverse Proxy To Zimbra Proxy |
Introduction
Zimbra Proxy is based on nginx. The configuration of reverse proxies is done in templates files.
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.
