From: André Malo Date: Wed, 9 Nov 2011 20:26:02 +0000 (+0000) Subject: update transformation X-Git-Tag: 2.3.16~225 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b7ca077a387fdda3c39f240eec5cf2ce710cec27;p=apache 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 49791d315f..247c071289 100644 --- a/docs/manual/mod/mod_proxy_ajp.html.en +++ b/docs/manual/mod/mod_proxy_ajp.html.en @@ -67,13 +67,13 @@

Usage

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 ajp:// prefix: + an HTTP reverse proxy, but uses the ajp:// prefix:

Simple Reverse Proxy

ProxyPass /app ajp://backend.example.com:8009/app

- Balancers may also be used: +

Balancers may also be used:

Balancer Reverse Proxy

<Proxy balancer://cluster>
@@ -84,22 +84,24 @@ </Proxy>
ProxyPass /app balancer://cluster/app

-

- Note that usually no + +

Note that usually no ProxyPassReverse 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. -

- The main exception is when the URL path on the proxy differs from that on the + rewriting is necessary.

+ +

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 ajp:// URL), for example: + original host URL (not the backend ajp:// URL), for + example:

Rewriting Proxied Path

ProxyPass /apps/foo ajp://backend.example.com:8009/foo
ProxyPassReverse /apps/foo http://www.example.com/foo

- However, it is usually better to deploy the application on the backend +

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.

top
diff --git a/docs/manual/mod/mod_proxy_ajp.xml.ja b/docs/manual/mod/mod_proxy_ajp.xml.ja index 391a524d8b..835f9c507a 100644 --- a/docs/manual/mod/mod_proxy_ajp.xml.ja +++ b/docs/manual/mod/mod_proxy_ajp.xml.ja @@ -1,7 +1,7 @@ - +