Template:ZimbraProxyManual: Difference between revisions

mNo edit summary
(Adding additional reverse proxy to Zimbra Proxy)
Line 20: Line 20:
----
----


{|  width="100%" border="0"
|  bgcolor="orange" | [[Image:Attention.png]] - Please excuse the inline draft notes, this is a working draft that is actively being worked on as a part of our proxy documentation rewrite project. Ajcody - Sept. 10, 2014
|}


<noinclude>
== Adding additional reverse proxy to Zimbra Proxy ==
Zimbra Proxy is based on nginx. The configuration of reverse proxies is done in templates files.


In order to use this template, type the following Wikitext at the bottom of the article you are editing:


<nowiki>{{ZimbraProxyManual}}</nowiki>
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:


[[Category:Templates]]
nano /opt/zimbra/conf/nginx/templates/nginx.conf.web.https.default.template
</noinclude>
 
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.

Revision as of 18:26, 16 September 2015

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


Adding additional reverse proxy to Zimbra Proxy

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.

Jump to: navigation, search