httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From n.@apache.org
Subject svn commit: r1199951 - /httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml
Date Wed, 09 Nov 2011 20:29:04 GMT
Author: nd
Date: Wed Nov  9 20:29:04 2011
New Revision: 1199951

URL: http://svn.apache.org/viewvc?rev=1199951&view=rev
Log:
examples are block elements and cannot occur within <p> elements.

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml?rev=1199951&r1=1199950&r2=1199951&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_proxy_ajp.xml Wed Nov  9 20:29:04 2011
@@ -54,13 +54,13 @@
 <section id="usage"><title>Usage</title>
     <p>This module is used to reverse proxy to a backend application server
     (e.g. Apache Tomcat) using the AJP13 protocol. The usage is similar to
-    an HTTP reverse proxy, but uses the <code>ajp://</code> prefix:
+    an HTTP reverse proxy, but uses the <code>ajp://</code> prefix:</p>
 
     <example><title>Simple Reverse Proxy</title>
     ProxyPass /app ajp://backend.example.com:8009/app
     </example>
 
-    Balancers may also be used:
+    <p>Balancers may also be used:</p>
     <example><title>Balancer Reverse Proxy</title>
       &lt;Proxy balancer://cluster&gt;<br />
       <indent>
@@ -71,22 +71,25 @@
       &lt;/Proxy&gt;<br />
       ProxyPass /app balancer://cluster/app
     </example>
-    </p><p>
-    Note that usually no
+    <p>Note that usually no
     <directive module="mod_proxy">ProxyPassReverse</directive>
     directive is necessary. The AJP request includes the original host
     header given to the proxy, and the application server can be expected
     to generate self-referential headers relative to this host, so no
     rewriting is necessary.
-    </p><p>
-    The main exception is when the URL path on the proxy differs from that on the
+    </p>
+
+    <p>The main exception is when the URL path on the proxy differs from that
+    on the
     backend. In this case, a redirect header can be rewritten relative to the
-    original host URL (not the backend <code>ajp://</code> URL), for example:
+    original host URL (not the backend <code>ajp://</code> URL), for
+    example:</p>
     <example><title>Rewriting Proxied Path</title>
       ProxyPass /apps/foo ajp://backend.example.com:8009/foo<br />
       ProxyPassReverse /apps/foo http://www.example.com/foo
     </example>
-    However, it is usually better to deploy the application on the backend
+
+    <p>However, it is usually better to deploy the application on the backend
     server at the same path as the proxy rather than to take this approach.
     </p>
 </section>



Mime
View raw message