You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ja...@apache.org on 2013/10/09 09:15:29 UTC
svn commit: r1530514 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_html.xml
Author: jailletc36
Date: Wed Oct 9 07:15:29 2013
New Revision: 1530514
URL: http://svn.apache.org/r1530514
Log:
Break long lines.
Add missing <code></code>
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_proxy_html.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_html.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_html.xml?rev=1530514&r1=1530513&r2=1530514&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_html.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_html.xml Wed Oct 9 07:15:29 2013
@@ -32,9 +32,21 @@ from Clients' networks in a proxy contex
for earlier 2.x versions</compatibility>
<summary>
- <p>This module provides 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 ProxyPassReverse directive does for HTTP headers, and is an essential component of a reverse proxy.</p>
-
-<p>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 <code>www.example.com</code>, they may wish to provide a gateway to the application server at <code>http://www.example.com/appserver/</code>. When the application server links to itself, those links need to be rewritten to work through the gateway. mod_proxy_html serves to rewrite <code><a href="http://appserver.example.com/foo/bar.html">foobar</a></code> to <code><a href="http://www.example.com/appserver/foo/bar.html">foobar</a></code> making it accessible from outside.</p>
+<p>This module provides 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 ProxyPassReverse directive does
+for HTTP headers, and is an essential component of a reverse proxy.</p>
+
+<p>For example, if a company has an application server at
+<code>appserver.example.com</code> that is only visible from within
+the company's internal network, and a public webserver
+<code>www.example.com</code>, they may wish to provide a gateway to the
+application server at <code>http://www.example.com/appserver/</code>.
+When the application server links to itself, those links need to be
+rewritten to work through the gateway. mod_proxy_html serves to rewrite
+<code><a href="http://appserver.example.com/foo/bar.html">foobar</a></code> to
+<code><a href="http://www.example.com/appserver/foo/bar.html">foobar</a></code>
+making it accessible from outside.</p>
<p>mod_proxy_html was originally developed at WebÞing, whose
extensive <a href="http://apache.webthing.com/mod_proxy_html/"