Apache 2 Integration
1. Configuring Apache 2 Reverse Proxy
This is required to forward any requests to /unblu/ to the backend unblu server.
1.1. Runtime Dependencies
mod_unblufilter needs a working proxy configuration, if you do not have a custom proxy setup please install the following Apache modules:
If you have your own proxy setup in Apache, make sure that it is a non-caching reverse proxy that does not deliver own (cached) content. Cached content is not processed by mod_unblufilter and cannot be co-browsed.
1.2. Module Configuration
dist package of
mod_unblufilter provides a
config directory containing a number of example configurations for various platforms. These examples are more accurate than descriptions in this document.
1.2.1. Configuration File Excerpt
The following is an working Apache example proxy configuration using mod_proxy:
1.2.2. Reverse proxy settings
The following settings are "generic" and usually need no adaptation:
IfModule !mod_proxy.c: load
mod_proxyif not loaded already
IfModule !mod_proxy_http.c: load
mod_proxy_httpif not loaded already
ProxyRequests: Configure this as a reverse proxy (thus set to "no" to disable forward proxy capabilities)
Proxy section: configure access control to proxy (allow all)
Some systems such as Debian Linux by default do not may not be compiled to support dynamically loading of modules, however they provide helper utilities to manage apache modules such as a2enmod and a2dismod.
In such an environment please enable the apache modules by executing
[sudo] a2endmod proxy proxy_http
In such a setup the above LoadModule commands will likely not work but aren't needed either.
The following two lines require adaptation: "unbluserver" must be replaced with the hostname plus port (if non-standard) of the backend unblu server.
/unblurequests to be proxied
ProxyPassReverse: Make sure response headers are adapted accordingly to have a transparent reverse proxy