mod_proxy_html has now been relicensed and incorporated into the core Apache HTTPD distribution at apache.org from HTTPD 2.4. That version is now likely to be more up-to-date than this one.
Here a one-line bug-fix has been introduced since version 3.1.3. If you downloaded the bundled package from here, you should apply the patch before compiling. The bug won't affect most users and is not a security issue, so if you are already using mod_proxy_html successfully there's nothing to do.
mod_proxy_html is an output filter to rewrite HTML links in a proxy
situation, to ensure that links work for users outside the proxy.
It serves the same purpose as Apache's
directive does for HTTP headers, and is an essential component of a
For example, if a company has an application server at appserver.example.com that is only visible from within the company's internal network, and a public webserver www.example.com, they may wish to provide a gateway to the application server at http://www.example.com/appserver/. When the application server links to itself, those links need to be rewritten to work through the gateway. mod_proxy_html serves to rewrite <a href="http://appserver.example.com/foo/bar.html">foobar</a> to <a href="http://www.example.com/appserver/foo/bar.html">foobar</a> making it accessible from outside.
April 2006 Added a new FAQ to deal with some of the questions people commonly mail me with.
For more recent history, see updates at apache.org.
The current bugfix release is 3.1.4. The most recent single-line bugfix is dated 2013-02-04.
The origins and history of mod_proxy_html are documented in a separate page.
The original capabilities of mod_proxy_html are:
Important changes from 1.x to 2.x include:
meta http-equivHTML elements to real HTTP headers.
Important changes from 2.x to 3.x include:
With these new features, mod_proxy_html might find applications outside a
proxy context, and an environment variable
can be used to force it to process non-proxied pages.
But reverse-proxying remains its primary purpose, while
mod_publisher offers a far wider range
of capabilities for other applications.
Important Note: Configuration has changed:
ProxyHTMLEnabledirective, and mod_proxy_html will configure both itself and mod_xml2enc for you.
We now have three documents: a tutorial on reverse proxying (including basic use of mod_proxy_html), a user guide, and a configuration guide. Please read the tutorial first, unless you already know it all!
A tutorial on reverse proxying with Apache by the author of this module is available at ApacheTutor. This offers an in-depth overview of the problem solved by this module, in context.
Reference documentation for the configuration directives implemented by mod_proxy_html.
This focuses on the module itself, separate from the context of the problem it solves.
Some questions come up repeatedly (sometimes in the form of bug reports, feature requests, or patches). Please see the FAQ before mailing anything.
Support is available from the developer for paying clients.
Support is also available on an ad-hoc basis from the apache community, including the users mailinglist, and the #httpd channel on irc.freenode.org.
mod_proxy_html.c source code is available from here under the GNU General Public License (GPL) Version 2.
NOTE: If you downloaded the bundle before October 30th, you should upgrade your copy of mod_xml2enc to 1.0.3, which fixes a bug. The current bundle includes the bugfix.
The current version from apache.org has been relicensed under the Apache License. If you are redistributing anything derived from mod_proxy_html, you should use the source whose license best meets your needs. If neither license is appropriate, we can consider relicensing on your own terms for payment.
Users of the FreeBSD port of mod_proxy_html, please see this fix.