Configuring the Openfire server in a reverse proxy environment
If you are using a reverse proxy setup for accessing an application, you need to add some rules to the reverse proxy configuration so that the HTTP traffic for chat is correctly re-directed. The example in this topic shows the configuration of the Openfire server when configuring reverse proxy for the Apache server.
To configure the Openfire server for reverse proxy
Add the following entries in the Apache httpd.conf file:
ProxyPass
/crossdomain.xml
http://:port/crossdomain.xml
ProxyPassReverse
/crossdomain.xml
http://:port/crossdomain.xml
ProxyPass
/http-bind/
http://:port/http-bind/
ProxyPassReverse
/http-bind/
http://:port/http-bind/
- Modify the ChatConfig entry as follows:
XMPPServerName = <The HTTP server name>
XMPPServerPort = 80 (for HTTP) OR 443 (for HTTPS)
XMPPPortIsSecure = false (for HTTP) OR true (for HTTPS)
In such cases, the browser communicates with the Openfire server using the http server name and not the OpenFire server name. - Make sure that the host name specified in the Openfire configuration is changed to match the name that the browser uses to access the server:
- Open the Openfire Administration Console (default link is http://:9090) and login as an administrator.
- On the Server Information page, scroll down and click Edit Properties.
- Enter the server name in the Server Name field and click Save properties.
- Restart the Openfire server.
- After the Openfire server host name is changed, add the proper certificates to the Openfire server for that domain name.
For more information, see the Openfire SSL Guide (http://www.igniterealtime.org/projects/openfire/documentation.jsp).
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*