diff options
| author | André Malo <nd@apache.org> | 2011-11-09 20:23:46 +0000 |
|---|---|---|
| committer | André Malo <nd@apache.org> | 2011-11-09 20:23:46 +0000 |
| commit | b568fa26beb13d4ed351a08e78033d4c7ea7d176 (patch) | |
| tree | ad9ce50f201ca32564a59fcf7e0669676c3e40b9 | |
| parent | 3db0ad2749b84460234260d750ae7df84f2cd8a5 (diff) | |
| download | httpd-b568fa26beb13d4ed351a08e78033d4c7ea7d176.tar.gz | |
examples are block elements and cannot occur within <p> elements.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1199948 13f79535-47bb-0310-9956-ffa450edef68
| -rw-r--r-- | docs/manual/mod/mod_proxy_ajp.xml | 20 |
1 files changed, 11 insertions, 9 deletions
diff --git a/docs/manual/mod/mod_proxy_ajp.xml b/docs/manual/mod/mod_proxy_ajp.xml index c501ad2b5f..10f25ccdbf 100644 --- a/docs/manual/mod/mod_proxy_ajp.xml +++ b/docs/manual/mod/mod_proxy_ajp.xml @@ -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> <Proxy balancer://cluster><br /> <indent> @@ -71,22 +71,24 @@ </Proxy><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 + 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> <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> |