update transformation

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1199949 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_proxy_ajp.html.en b/docs/manual/mod/mod_proxy_ajp.html.en
index 49791d315fb06679d37ecd905921941ef98a782e..247c0712895551aee314bac6bf9d3b962d222b94 100644 (file)
--- a/docs/manual/mod/mod_proxy_ajp.html.en
+++ b/docs/manual/mod/mod_proxy_ajp.html.en
@@ -67,13 +67,13 @@
 <h2><a name="usage" id="usage">Usage</a></h2>
     <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>
 
     <div class="example"><h3>Simple Reverse Proxy</h3><p><code>
     ProxyPass /app ajp://backend.example.com:8009/app
     </code></p></div>
 
-    Balancers may also be used:
+    <p>Balancers may also be used:</p>
     <div class="example"><h3>Balancer Reverse Proxy</h3><p><code>
       &lt;Proxy balancer://cluster&gt;<br />
       <span class="indent">
@@ -84,22 +84,24 @@
       &lt;/Proxy&gt;<br />
       ProxyPass /app balancer://cluster/app
     </code></p></div>
-    </p><p>
-    Note that usually no
+
+    <p>Note that usually no
     <code class="directive"><a href="../mod/mod_proxy.html#proxypassreverse">ProxyPassReverse</a></code>
     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
+    rewriting is necessary.</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>
     <div class="example"><h3>Rewriting Proxied Path</h3><p><code>
       ProxyPass /apps/foo ajp://backend.example.com:8009/foo<br />
       ProxyPassReverse /apps/foo http://www.example.com/foo
     </code></p></div>
-    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>
 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>

diff --git a/docs/manual/mod/mod_proxy_ajp.xml.ja b/docs/manual/mod/mod_proxy_ajp.xml.ja
index 391a524d8bb1c4813e1ac06197c9d33efe7d0845..835f9c507a267ba0e6f46006b67f0e3b7b2ae040 100644 (file)
--- a/docs/manual/mod/mod_proxy_ajp.xml.ja
+++ b/docs/manual/mod/mod_proxy_ajp.xml.ja
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" ?>
 <!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
 <?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 669473:1199554 (outdated) -->
+<!-- English Revision: 669473:1199948 (outdated) -->
 
 <!--
  Licensed to the Apache Software Foundation (ASF) under one or more