humbedooh at apache
Apr 26, 2012, 10:03 PM
Post #1 of 1
(21 views)
Permalink
|
|
svn commit: r1331217 - in /httpd/httpd/trunk/docs/manual/mod: mod_policy.xml mod_proxy.xml mod_proxy_ajp.xml mod_proxy_balancer.xml mod_proxy_fcgi.xml mod_proxy_ftp.xml mod_proxy_scgi.xml
|
|
Author: humbedooh
Date: Fri Apr 27 05:03:19 2012
New Revision: 1331217
URL: http://svn.apache.org/viewvc?rev=1331217&view=rev
Log:
Syntax updates for mod_p*.xml
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_policy.xml
httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml
httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml
httpd/httpd/trunk/docs/manual/mod/mod_proxy_ftp.xml
httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_policy.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_policy.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_policy.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_policy.xml Fri Apr 27 05:03:19 2012
@@ -193,50 +193,44 @@
<p>A typical configuration protecting a server serving static content
might be as follows:</p>
- <example>
- <Location /><br />
- <indent>
- SetOutputFilter POLICY_TYPE;POLICY_LENGTH;POLICY_KEEPALIVE;POLICY_VARY;POLICY_VALIDATION; \<br />
- <indent>
- POLICY_CONDITIONAL;POLICY_NOCACHE;POLICY_MAXAGE;POLICY_VERSION<br />
- </indent>
- <br />
- # content type must be present and valid, but can be anything<br />
- PolicyType enforce */*<br />
- <br />
- # reject if no explicitly declared content length<br />
- PolicyLength enforce<br />
- <br />
- # covered by the policy length filter<br />
- PolicyKeepalive ignore<br />
- <br />
- # reject if User-Agent appears within Vary headers<br />
- PolicyVary enforce User-Agent<br />
- <br />
- # we want to enforce validation<br />
- PolicyValidation enforce<br />
- <br />
- # non-functional conditional responses should be rejected<br />
- PolicyConditional enforce<br />
- <br />
- # no-cache responses should be rejected<br />
- PolicyNocache enforce<br />
- <br />
- # maxage must be at least a day<br />
- PolicyMaxage enforce 86400<br />
- <br />
- # request version can be anything<br />
- PolicyVersion ignore HTTP/1.1<br />
- </indent>
- </Location><br />
- <br />
- # suppress policy protection for server-status<br />
- <Location /server-status><br />
- <indent>
- PolicyFilter off<br />
- </indent>
- </Location><br />
- </example>
+ <highlight language="config">
+<Location />
+ SetOutputFilter POLICY_TYPE;POLICY_LENGTH;POLICY_KEEPALIVE;POLICY_VARY;POLICY_VALIDATION; \
+ POLICY_CONDITIONAL;POLICY_NOCACHE;POLICY_MAXAGE;POLICY_VERSION
+
+ # content type must be present and valid, but can be anything
+ PolicyType enforce */*
+
+ # reject if no explicitly declared content length
+ PolicyLength enforce
+
+ # covered by the policy length filter
+ PolicyKeepalive ignore
+
+ # reject if User-Agent appears within Vary headers
+ PolicyVary enforce User-Agent
+
+ # we want to enforce validation
+ PolicyValidation enforce
+
+ # non-functional conditional responses should be rejected
+ PolicyConditional enforce
+
+ # no-cache responses should be rejected
+ PolicyNocache enforce
+
+ # maxage must be at least a day
+ PolicyMaxage enforce 86400
+
+ # request version can be anything
+ PolicyVersion ignore HTTP/1.1
+</Location>
+
+# suppress policy protection for server-status
+<Location /server-status>
+ PolicyFilter off
+</Location>
+ </highlight>
</section>
@@ -255,19 +249,17 @@ later.</compatibility>
<p>Master switch to enable or disable policies for a given URL space.</p>
<example><title>Example</title>
- # enabled by default<br />
- <Location /><br />
- <indent>
- PolicyFilter on<br />
- </indent>
- </Location><br />
- <br />
- # suppress policy protection for server-status<br />
- <Location /server-status><br />
- <indent>
- PolicyFilter off<br />
- </indent>
- </Location><br />
+ <highlight language="config">
+# enabled by default
+<Location />
+ PolicyFilter on
+</Location>
+
+# suppress policy protection for server-status
+<Location /server-status>
+ PolicyFilter off
+</Location>
+</highlight>
</example>
</usage>
@@ -292,8 +284,10 @@ later.</compatibility>
be ignored.</p>
<example><title>Example</title>
- # downgrade if POLICY_CONTROL was present<br />
- PolicyEnvironment POLICY_CONTROL log ignore<br />
+ <highlight language="config">
+# downgrade if POLICY_CONTROL was present
+PolicyEnvironment POLICY_CONTROL log ignore
+ </highlight>
</example>
</usage>
@@ -315,8 +309,10 @@ later.</compatibility>
but wasn't will be rejected.</p>
<example><title>Example</title>
- # non-functional conditional responses should be rejected<br />
- PolicyConditional enforce<br />
+ <highlight language="config">
+# non-functional conditional responses should be rejected
+PolicyConditional enforce
+ </highlight>
</example>
</usage>
@@ -356,8 +352,10 @@ later.</compatibility>
<code>Content-Length</code> header will be rejected.</p>
<example><title>Example</title>
- # missing Content-Length header should be rejected<br />
- PolicyLength enforce<br />
+ <highlight language="config">
+# missing Content-Length header should be rejected
+PolicyLength enforce
+ </highlight>
</example>
</usage>
@@ -398,8 +396,10 @@ later.</compatibility>
of <code>chunked</code> will be rejected.</p>
<example><title>Example</title>
- # missing Content-Length or Transfer-Encoding should be rejected<br />
- PolicyKeepalive enforce<br />
+ <highlight language="config">
+# missing Content-Length or Transfer-Encoding should be rejected
+PolicyKeepalive enforce
+</highlight>
</example>
</usage>
@@ -440,13 +440,17 @@ later.</compatibility>
header does not match the given pattern or patterns will be rejected.</p>
<example><title>Example</title>
- # enforce json or XML<br />
- PolicyType enforce application/json text/xml<br />
+ <highlight language="config">
+# enforce json or XML
+PolicyType enforce application/json text/xml
+ </highlight>
</example>
<example><title>Example</title>
- # malformed content type should be rejected<br />
- PolicyType enforce */*<br />
+ <highlight language="config">
+# malformed content type should be rejected
+PolicyType enforce */*
+ </highlight>
</example>
</usage>
@@ -488,8 +492,10 @@ later.</compatibility>
rejected.</p>
<example><title>Example</title>
- # reject reponses with "User-Agent" listed in the Vary header<br />
- PolicyVary enforce User-Agent<br />
+ <highlight language="config">
+# reject reponses with "User-Agent" listed in the Vary header
+PolicyVary enforce User-Agent
+ </highlight>
</example>
</usage>
@@ -531,8 +537,10 @@ later.</compatibility>
either header is syntactically incorrect, will be rejected.</p>
<example><title>Example</title>
- # no ETag or Last-Modified will be rejected<br />
- PolicyValidation enforce<br />
+ <highlight language="config">
+# no ETag or Last-Modified will be rejected
+PolicyValidation enforce
+ </highlight>
</example>
</usage>
@@ -574,8 +582,10 @@ later.</compatibility>
be rejected.</p>
<example><title>Example</title>
- # Cache-Control: no-cache will be rejected<br />
- PolicyNocache enforce<br />
+ <highlight language="config">
+# Cache-Control: no-cache will be rejected
+PolicyNocache enforce
+ </highlight>
</example>
</usage>
@@ -618,8 +628,10 @@ later.</compatibility>
smaller than the given value, will be rejected.</p>
<example><title>Example</title>
- # reject responses with a freshness lifetime shorter than a day<br />
- PolicyMaxage enforce 86400<br />
+ <highlight language="config">
+# reject responses with a freshness lifetime shorter than a day
+PolicyMaxage enforce 86400
+ </highlight>
</example>
</usage>
@@ -660,8 +672,10 @@ later.</compatibility>
will be rejected.</p>
<example><title>Example</title>
- # reject requests with an HTTP version older than HTTP/1.1<br />
- PolicyVersion enforce HTTP/1.1<br />
+ <highlight language="config">
+# reject requests with an HTTP version older than HTTP/1.1
+PolicyVersion enforce HTTP/1.1
+ </highlight>
</example>
</usage>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.xml Fri Apr 27 05:03:19 2012
@@ -151,19 +151,21 @@
the documentation from <module>mod_cache</module>.</p>
<example><title>Reverse Proxy</title>
- ProxyPass /foo http://foo.example.com/bar<br />
- ProxyPassReverse /foo http://foo.example.com/bar
+ <highlight language="config">
+ProxyPass /foo http://foo.example.com/bar
+ProxyPassReverse /foo http://foo.example.com/bar
+ </highlight>
</example>
<example><title>Forward Proxy</title>
- ProxyRequests On<br />
- ProxyVia On<br />
- <br />
- <Proxy *><br />
- <indent>
- Require host internal.example.com<br />
- </indent>
- </Proxy>
+ <highlight language="config">
+ProxyRequests On
+ProxyVia On
+
+<Proxy *>
+ Require host internal.example.com
+</Proxy>
+ </highlight>
</example>
</section> <!-- /examples -->
@@ -187,29 +189,27 @@
<directive module="mod_proxy">ProxyPassMatch</directive> when used
for a reverse proxy:</p>
- <example>
+ <highlight language="config">
ProxyPass /example http://backend.example.com connectiontimeout=5 timeout=30
- </example>
+ </highlight>
<p>This will create a worker associated with the origin server URL
<code>http://backend.example.com</code> and using the given timeout
values. When used in a forward proxy, workers are usually defined
via the <directive module="mod_proxy">ProxySet</directive> directive:</p>
- <example>
+ <highlight language="config">
ProxySet http://backend.example.com connectiontimeout=5 timeout=30
- </example>
+ </highlight>
<p>or alternatively using <directive module="mod_proxy">Proxy</directive>
and <directive module="mod_proxy">ProxySet</directive>:</p>
- <example>
- <Proxy http://backend.example.com><br />
- <indent>
- ProxySet connectiontimeout=5 timeout=30
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+<Proxy http://backend.example.com>
+ ProxySet connectiontimeout=5 timeout=30
+</Proxy>
+ </highlight>
<p>Using explicitly configured workers in the forward mode is
not very common, because forward proxies usually communicate with many
@@ -225,10 +225,10 @@
<p>The URL identifying a direct worker is the URL of its
origin server including any path components given:</p>
- <example>
- ProxyPass /examples http://backend.example.com/examples<br />
- ProxyPass /docs http://backend.example.com/docs
- </example>
+ <highlight language="config">
+ProxyPass /examples http://backend.example.com/examples
+ProxyPass /docs http://backend.example.com/docs
+ </highlight>
<p>This example defines two different workers, each using a separate
connection pool and configuration.</p>
@@ -238,10 +238,10 @@
the URL of some worker is a leading substring of the URL of another
worker defined later in the configuration file. In the following example</p>
- <example>
- ProxyPass /apps http://backend.example.com/ timeout=60<br />
- ProxyPass /examples http://backend.example.com/examples timeout=10
- </example>
+ <highlight language="config">
+ProxyPass /apps http://backend.example.com/ timeout=60
+ProxyPass /examples http://backend.example.com/examples timeout=10
+ </highlight>
<p>the second worker isn't actually created. Instead the first
worker is used. The benefit is, that there is only one connection pool,
@@ -288,13 +288,11 @@
module="mod_proxy" type="section">Proxy</directive> control block as in
the following example:</p>
- <example>
- <Proxy *><br />
- <indent>
- Require ip 192.168.0<br />
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+<Proxy *>
+ Require ip 192.168.0
+</Proxy>
+ </highlight>
<p>For more information on access control directives, see
<module>mod_authz_host</module>.</p>
@@ -358,15 +356,13 @@
<p>These are the <code>force-proxy-request-1.0</code> and
<code>proxy-nokeepalive</code> notes.</p>
- <example>
- <Location /buggyappserver/><br />
- <indent>
- ProxyPass http://buggyappserver:7001/foo/<br />
- SetEnv force-proxy-request-1.0 1<br />
- SetEnv proxy-nokeepalive 1<br />
- </indent>
- </Location>
- </example>
+ <highlight language="config">
+<Location /buggyappserver/>
+ ProxyPass http://buggyappserver:7001/foo/
+ SetEnv force-proxy-request-1.0 1
+ SetEnv proxy-nokeepalive 1
+</Location>
+ </highlight>
</section> <!-- /envsettings -->
@@ -452,25 +448,21 @@
<code>yournetwork.example.com</code> to access content via your proxy
server:</p>
- <example>
- <Proxy *><br />
- <indent>
- Require host yournetwork.example.com<br />
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+<Proxy *>
+ Require host yournetwork.example.com
+</Proxy>
+ </highlight>
<p>The following example will process all files in the <code>foo</code>
directory of <code>example.com</code> through the <code>INCLUDES</code>
filter when they are sent through the proxy server:</p>
- <example>
- <Proxy http://example.com/foo/*><br />
- <indent>
- SetOutputFilter INCLUDES<br />
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+<Proxy http://example.com/foo/*>
+ SetOutputFilter INCLUDES
+</Proxy>
+ </highlight>
</usage>
<seealso><directive type="section" module="mod_proxy">ProxyMatch</directive></seealso>
@@ -605,9 +597,11 @@ context in 2.3.3 and later.</compatibili
are forwarded through the remote proxy using the HTTP CONNECT method.</p>
<example><title>Example</title>
- ProxyRemote http://goodguys.example.com/ http://mirrorguys.example.com:8000<br />
- ProxyRemote * http://cleverproxy.localdomain<br />
- ProxyRemote ftp http://ftpproxy.mydomain:8080
+ <highlight language="config">
+ProxyRemote http://goodguys.example.com/ http://mirrorguys.example.com:8000
+ProxyRemote * http://cleverproxy.localdomain
+ProxyRemote ftp http://ftpproxy.mydomain:8080
+ </highlight>
</example>
<p>In the last example, the proxy will forward FTP requests, encapsulated
@@ -697,30 +691,28 @@ expressions</description>
<directive module="mod_proxy">ProxyPass</directive> directive.</p>
<example>
- <Proxy balancer://hotcluster><br />
- <indent>
- BalancerMember http://www2.example.com:8080 loadfactor=1<br />
- BalancerMember http://www3.example.com:8080 loadfactor=2<br />
- ProxySet lbmethod=bytraffic<br />
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+<Proxy balancer://hotcluster>
+ BalancerMember http://www2.example.com:8080 loadfactor=1
+ BalancerMember http://www3.example.com:8080 loadfactor=2
+ ProxySet lbmethod=bytraffic
+</Proxy>
+ </highlight>
+ </example>
+
+ <highlight language="config">
+<Proxy http://backend>
+ ProxySet keepalive=On
+</Proxy>
+ </highlight>
- <example>
- <Proxy http://backend><br />
- <indent>
- ProxySet keepalive=On<br />
- </indent>
- </Proxy>
- </example>
-
- <example>
+ <highlight language="config">
ProxySet balancer://foo lbmethod=bytraffic timeout=15
- </example>
+ </highlight>
- <example>
+ <highlight language="config">
ProxySet ajp://backend:7001 timeout=15
- </example>
+ </highlight>
<note type="warning"><title>Warning</title>
<p>Keep in mind that the same parameter key can have a different meaning
@@ -757,13 +749,11 @@ expressions</description>
<p>Suppose the local server has address <code>http://example.com/</code>;
then</p>
- <example>
- <Location /mirror/foo/><br />
- <indent>
- ProxyPass http://backend.example.com/<br />
- </indent>
- </Location><br />
- </example>
+ <highlight language="config">
+<Location /mirror/foo/>
+ ProxyPass http://backend.example.com/
+</Location>
+ </highlight>
<p>will cause a local request for
<code>http://example.com/mirror/foo/bar</code> to be internally converted
@@ -774,9 +764,9 @@ expressions</description>
the below syntax is that it allows for dynamic control via the
<a href="mod_proxy_balancer.html#balancer_manager">Balancer Manager</a> interface:</p>
- <example>
+ <highlight language="config">
ProxyPass /mirror/foo/ http://backend.example.com/
- </example>
+ </highlight>
<note type="warning">
<p>If the first argument ends with a trailing <strong>/</strong>, the second
@@ -789,23 +779,19 @@ expressions</description>
<p>The <code>!</code> directive is useful in situations where you don't want
to reverse-proxy a subdirectory, <em>e.g.</em></p>
- <example>
- <Location /mirror/foo/><br />
- <indent>
- ProxyPass http://backend.example.com/<br />
- </indent>
- </Location><br />
- <Location /mirror/foo/i><br />
- <indent>
- ProxyPass !<br />
- </indent>
- </Location><br />
- </example>
-
- <example>
- ProxyPass /mirror/foo/i !<br />
- ProxyPass /mirror/foo http://backend.example.com
- </example>
+ <highlight language="config">
+<Location /mirror/foo/>
+ ProxyPass http://backend.example.com/
+</Location>
+<Location /mirror/foo/i>
+ ProxyPass !
+</Location>
+ </highlight>
+
+ <highlight language="config">
+ProxyPass /mirror/foo/i !
+ProxyPass /mirror/foo http://backend.example.com
+ </highlight>
<p>will proxy all requests to <code>/mirror/foo</code> to
<code>backend.example.com</code> <em>except</em> requests made to
@@ -1116,33 +1102,29 @@ expressions</description>
</table>
<p>A sample balancer setup</p>
- <example>
- ProxyPass /special-area http://special.example.com smax=5 max=10<br />
- ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On<br />
- <Proxy balancer://mycluster><br />
- <indent>
- BalancerMember ajp://1.2.3.4:8009<br />
- BalancerMember ajp://1.2.3.5:8009 loadfactor=20<br />
- # Less powerful server, don't send as many requests there,<br />
- BalancerMember ajp://1.2.3.6:8009 loadfactor=5<br />
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+ProxyPass /special-area http://special.example.com smax=5 max=10
+ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
+<Proxy balancer://mycluster>
+ BalancerMember ajp://1.2.3.4:8009
+ BalancerMember ajp://1.2.3.5:8009 loadfactor=20
+ # Less powerful server, don't send as many requests there,
+ BalancerMember ajp://1.2.3.6:8009 loadfactor=5
+</Proxy>
+ </highlight>
<p>Setting up a hot-standby, that will only be used if no other
members are available</p>
- <example>
- ProxyPass / balancer://hotcluster/ <br />
- <Proxy balancer://hotcluster><br />
- <indent>
- BalancerMember ajp://1.2.3.4:8009 loadfactor=1<br />
- BalancerMember ajp://1.2.3.5:8009 loadfactor=2<br />
- # The below is the hot standby<br />
- BalancerMember ajp://1.2.3.6:8009 status=+H<br />
- ProxySet lbmethod=bytraffic
- </indent>
- </Proxy>
- </example>
+ <highlight language="config">
+ProxyPass / balancer://hotcluster/
+<Proxy balancer://hotcluster>
+ BalancerMember ajp://1.2.3.4:8009 loadfactor=1
+ BalancerMember ajp://1.2.3.5:8009 loadfactor=2
+ # The below is the hot standby
+ BalancerMember ajp://1.2.3.6:8009 status=+H
+ ProxySet lbmethod=bytraffic
+</Proxy>
+ </highlight>
<p>Normally, mod_proxy will canonicalise ProxyPassed URLs.
But this may be incompatible with some backends, particularly those
@@ -1204,9 +1186,9 @@ expressions</description>
<p>Suppose the local server has address <code>http://example.com/</code>;
then</p>
- <example>
+ <highlight language="config">
ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com$1
- </example>
+ </highlight>
<p>will cause a local request for
<code>http://example.com/foo/bar.gif</code> to be internally converted
@@ -1215,15 +1197,15 @@ expressions</description>
<p>The URL argument must be parsable as a URL <em>before</em> regexp
substitutions (as well as after). This limits the matches you can use.
For instance, if we had used</p>
- <example>
+ <highlight language="config">
ProxyPassMatch ^(/.*\.gif)$ http://backend.example.com:8000$1
- </example>
+ </highlight>
<p>in our previous example, it would fail with a syntax error
at server startup. This is a bug (PR 46665 in the ASF bugzilla),
and the workaround is to reformulate the match:</p>
- <example>
+ <highlight language="config">
ProxyPassMatch ^/(.*\.gif)$ http://backend.example.com:8000/$1
- </example>
+ </highlight>
</note>
<p>The <code>!</code> directive is useful in situations where you don't want
to reverse-proxy a subdirectory.</p>
@@ -1282,12 +1264,12 @@ proxied server</description>
<p>For example, suppose the local server has address
<code>http://example.com/</code>; then</p>
- <example>
- ProxyPass /mirror/foo/ http://backend.example.com/<br />
- ProxyPassReverse /mirror/foo/ http://backend.example.com/<br />
- ProxyPassReverseCookieDomain backend.example.com public.example.com<br />
- ProxyPassReverseCookiePath / /mirror/foo/
- </example>
+ <highlight language="config">
+ProxyPass /mirror/foo/ http://backend.example.com/
+ProxyPassReverse /mirror/foo/ http://backend.example.com/
+ProxyPassReverseCookieDomain backend.example.com public.example.com
+ProxyPassReverseCookiePath / /mirror/foo/
+ </highlight>
<p>will not only cause a local request for the
<code>http://example.com/mirror/foo/bar</code> to be internally converted
@@ -1369,9 +1351,9 @@ reverse proxy. This directive rewrites t
In the example given with
<directive module="mod_proxy">ProxyPassReverse</directive>, the directive:
</p>
- <example>
+ <highlight language="config">
ProxyPassReverseCookiePath / /mirror/foo/
- </example>
+ </highlight>
<p>
will rewrite a cookie with backend path <code>/</code> (or
<code>/example</code> or, in fact, anything) to <code>/mirror/foo/</code>.
@@ -1398,7 +1380,9 @@ proxied</description>
well. That may slow down the startup time of the server.</p>
<example><title>Example</title>
+ <highlight language="config">
ProxyBlock news.example.com auctions.example.com friends.example.com
+ </highlight>
</example>
<p>Note that <code>example</code> would also be sufficient to match any
@@ -1408,9 +1392,9 @@ proxied</description>
<p>Note also that</p>
- <example>
+ <highlight language="config">
ProxyBlock *
- </example>
+ </highlight>
<p>blocks connections to all sites.</p>
</usage>
@@ -1433,7 +1417,9 @@ connections</description>
be used.</p>
<example><title>Example</title>
+ <highlight language="config">
ProxyReceiveBufferSize 2048
+ </highlight>
</example>
</usage>
</directivesynopsis>
@@ -1482,7 +1468,9 @@ through</description>
be set to prevent infinite proxy loops, or a DoS attack.</p>
<example><title>Example</title>
+ <highlight language="config">
ProxyMaxForwards 15
+ </highlight>
</example>
<p>Note that setting <directive>ProxyMaxForwards</directive> is a
@@ -1512,8 +1500,10 @@ directly</description>
<directive module="mod_proxy">ProxyRemote</directive> proxy server(s).</p>
<example><title>Example</title>
- ProxyRemote * http://firewall.example.com:81<br />
- NoProxy .example.com 192.168.112.0/21
+ <highlight language="config">
+ProxyRemote * http://firewall.example.com:81
+NoProxy .example.com 192.168.112.0/21
+ </highlight>
</example>
<p>The <var>host</var> arguments to the <directive>NoProxy</directive>
@@ -1652,9 +1642,11 @@ directly</description>
will be generated.</p>
<example><title>Example</title>
+ <highlight language="config">
ProxyRemote * http://firewall.example.com:81<br />
NoProxy .example.com 192.168.112.0/21<br />
ProxyDomain .example.com
+ </highlight>
</example>
</usage>
</directivesynopsis>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml Fri Apr 27 05:03:19 2012
@@ -57,19 +57,21 @@
an HTTP reverse proxy, but uses the <code>ajp://</code> prefix:</p>
<example><title>Simple Reverse Proxy</title>
+ <highlight language="config">
ProxyPass /app ajp://backend.example.com:8009/app
+ </highlight>
</example>
<p>Balancers may also be used:</p>
<example><title>Balancer Reverse Proxy</title>
- <Proxy balancer://cluster><br />
- <indent>
- BalancerMember ajp://app1.example.com:8009 loadfactor=1<br />
- BalancerMember ajp://app2.example.com:8009 loadfactor=2<br />
- ProxySet lbmethod=bytraffic<br />
- </indent>
- </Proxy><br />
- ProxyPass /app balancer://cluster/app
+ <highlight language="config">
+<Proxy balancer://cluster>
+ BalancerMember ajp://app1.example.com:8009 loadfactor=1
+ BalancerMember ajp://app2.example.com:8009 loadfactor=2
+ ProxySet lbmethod=bytraffic
+</Proxy>
+ProxyPass /app balancer://cluster/app
+ </highlight>
</example>
<p>Note that usually no
@@ -85,8 +87,10 @@
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
+ <highlight language="config">
+ProxyPass /apps/foo ajp://backend.example.com:8009/foo
+ProxyPassReverse /apps/foo http://www.example.com/foo
+ </highlight>
</example>
<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.
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_balancer.xml Fri Apr 27 05:03:19 2012
@@ -91,31 +91,30 @@
load balancing between two back-end servers:
</p>
- <example>
- <Proxy balancer://mycluster><br />
- BalancerMember http://192.168.1.50:80<br />
- BalancerMember http://192.168.1.51:80<br />
- </Proxy><br />
- ProxyPass /test balancer://mycluster<br />
- ProxyPassReverse /test balancer://mycluster
- </example>
+ <highlight language="config">
+<Proxy balancer://mycluster>
+ BalancerMember http://192.168.1.50:80
+ BalancerMember http://192.168.1.51:80
+</Proxy>
+ProxyPass /test balancer://mycluster
+ProxyPassReverse /test balancer://mycluster
+ </highlight>
<p>Another example of how to provide load balancing with stickyness
using <module>mod_headers</module>, even if the back-end server does
not set a suitable session cookie:
</p>
- <example>
- Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/"
- env=BALANCER_ROUTE_CHANGED<br />
- <Proxy balancer://mycluster><br />
- BalancerMember http://192.168.1.50:80 route=1<br />
- BalancerMember http://192.168.1.51:80 route=2<br />
- ProxySet stickysession=ROUTEID<br />
- </Proxy><br />
- ProxyPass /test balancer://mycluster<br />
- ProxyPassReverse /test balancer://mycluster
- </example>
+ <highlight language="config">
+Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
+<Proxy balancer://mycluster>
+ BalancerMember http://192.168.1.50:80 route=1
+ BalancerMember http://192.168.1.51:80 route=2
+ ProxySet stickysession=ROUTEID
+</Proxy>
+ProxyPass /test balancer://mycluster
+ProxyPassReverse /test balancer://mycluster
+ </highlight>
</section>
<section id="environment">
@@ -188,13 +187,12 @@
<p>To enable load balancer management for browsers from the example.com
domain add this code to your <code>httpd.conf</code>
configuration file</p>
-<example>
- <Location /balancer-manager><br />
- SetHandler balancer-manager<br />
-<br />
- Require host example.com<br />
- </Location>
-</example>
+<highlight language="config">
+<Location /balancer-manager>
+ SetHandler balancer-manager
+ Require host example.com
+</Location>
+</highlight>
<p>You can now access load balancer manager by using a Web browser
to access the page
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml Fri Apr 27 05:03:19 2012
@@ -61,7 +61,9 @@
enable <module>mod_proxy</module> and <module>mod_proxy_fcgi</module>.</p>
<example><title>Single application instance</title>
+ <highlight language="config">
ProxyPass /myapp/ fcgi://localhost:4000/
+ </highlight>
</example>
<p>This application should be able to handle multiple concurrent
@@ -76,7 +78,9 @@
the following example:</p>
<example><title>Single application instance, no connection reuse</title>
+ <highlight language="config">
ProxyPass /myapp/ fcgi://localhost:4000/ disablereuse=on
+ </highlight>
</example>
<p>The balanced gateway needs <module>mod_proxy_balancer</module> and
@@ -86,13 +90,13 @@
default, and will be used for this example configuration.</p>
<example><title>Balanced gateway to multiple application instances</title>
- ProxyPass /myapp/ balancer://myappcluster/<br />
- <Proxy balancer://myappcluster/><br />
- <indent>
- BalancerMember fcgi://localhost:4000/<br />
- BalancerMember fcgi://localhost:4001/<br />
- </indent>
- </Proxy>
+ <highlight language="config">
+ProxyPass /myapp/ balancer://myappcluster/
+<Proxy balancer://myappcluster/>
+ BalancerMember fcgi://localhost:4000/
+ BalancerMember fcgi://localhost:4001/
+</Proxy>
+ </highlight>
</example>
</section>
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_ftp.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_ftp.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_ftp.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_ftp.xml Fri Apr 27 05:03:19 2012
@@ -59,7 +59,7 @@
</example>
<p>Alternatively you may prefer to default everything to binary:</p>
<example>
-<pre>ForceType application/octet-stream</pre>
+ <highlight language="config">ForceType application/octet-stream</highlight>
</example>
</section> <!-- /mimetypes -->
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.xml?rev=1331217&r1=1331216&r2=1331217&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_scgi.xml Fri Apr 27 05:03:19 2012
@@ -55,7 +55,9 @@
enable <module>mod_proxy</module> and <module>mod_proxy_scgi</module>.</p>
<example><title>Simple gateway</title>
+ <highlight language="config">
ProxyPass /scgi-bin/ scgi://localhost:4000/
+ </highlight>
</example>
<p>The balanced gateway needs <module>mod_proxy_balancer</module> and
@@ -65,13 +67,13 @@
default, and will be used for this example configuration.</p>
<example><title>Balanced gateway</title>
- ProxyPass /scgi-bin/ balancer://somecluster/<br />
- <Proxy balancer://somecluster/><br />
- <indent>
- BalancerMember scgi://localhost:4000/<br />
- BalancerMember scgi://localhost:4001/<br />
- </indent>
- </Proxy>
+ <highlight language="config">
+ProxyPass /scgi-bin/ balancer://somecluster/
+<Proxy balancer://somecluster/>
+ BalancerMember scgi://localhost:4000/
+ BalancerMember scgi://localhost:4001/
+</Proxy>
+ </highlight>
</example>
</section>
@@ -124,11 +126,13 @@ header</description>
</dl>
<example><title>Example</title>
- # Use the default header (X-Sendfile)<br />
- ProxySCGISendfile On<br />
- <br />
- # Use a different header<br />
+ <highlight language="config">
+ # Use the default header (X-Sendfile)
+ ProxySCGISendfile On
+
+ # Use a different header
ProxySCGISendfile X-Send-Static
+ </highlight>
</example>
</usage>
</directivesynopsis>
@@ -156,7 +160,9 @@ backend</description>
feature.</p>
<example><title>Example</title>
+ <highlight language="config">
ProxySCGIInternalRedirect Off
+ </highlight>
</example>
</usage>
</directivesynopsis>
|
