Warning
You are looking at documentation for an older release. Not what you want? See the current release documentation.
It may be necessary to use an HTTP server as a front-end (aka a reverse-proxy) for your eXo Platform application server to allow :
- Accessing more than one application server on the same host;
- Accessing these app servers with the separate DNS names, without adding a port to the URL;
- Serving maintenance pages if the server is not available.
- Instrumenting your http request (for Single Sign on authentication for example)
- Caching and/or load-balancing
- Improving security with server isolation
This diagram represents a standard deployment with a reverse proxy
We recommand to use the http protocol as communication protocol between the HTTP proxy and the eXo Platform server as it's simpler to configure than the AJP protocol for the same performances.