From 6fa905da372240f7c1c821557adecd3bdcb61f8d Mon Sep 17 00:00:00 2001 From: Luca Toscano Date: Sun, 24 Jun 2018 10:33:06 +0000 Subject: [PATCH] documentation rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1834245 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_proxy.html.en | 21 ++++++++++++++------- docs/manual/mod/mod_proxy.xml.fr | 2 +- docs/manual/mod/mod_proxy.xml.ja | 2 +- 3 files changed, 16 insertions(+), 9 deletions(-) diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index 77ba17e823..cbdaea57f5 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -1503,13 +1503,15 @@ ProxyPass "/" "balancer://mycluster/" stickysession=JSESSIONID|jsessionid nofail httpd 2.4.1 and later) prevents this.

The optional interpolate keyword, in combination with - ProxyPassInterpolateEnv, causes the ProxyPass + ProxyPassInterpolateEnv, causes the ProxyPass to interpolate environment variables, using the syntax ${VARNAME}. Note that many of the standard CGI-derived environment variables will not exist when this interpolation happens, so you may still have to resort to mod_rewrite - for complex rules. Also note that interpolation is not supported - within the scheme/hostname/port portion of a URL. Dynamic determination of + for complex rules. Also note that interpolation is supported + within the scheme/hostname/port portion of a URL only for variables that + are available when the directive is parsed + (like Define). Dynamic determination of those fields can be accomplished with mod_rewrite. The following example describes how to use mod_rewrite to dynamically set the scheme to http or https:

@@ -1573,12 +1575,17 @@ ProxyPassReverse "/mirror/foo/" "https://backend.example.com/" and causes them to substitute the value of an environment variable varname for the string ${varname} in configuration directives if the interpolate option is set.

-

The scheme/hostname/port portion of ProxyPass cannot - contain variables, please consider using mod_rewrite instead.

-

Keep this turned off (for server performance) unless you need it! +

The scheme/hostname/port portion of ProxyPass may + contain variables, but only the ones available when the directive is parsed + (for example, using Define). + For all the other use cases, please consider using + mod_rewrite instead.

+

Performance warning

+

Keep this turned off unless you need it! Adding variables to ProxyPass for example may lead to - using the default mod_proxy's workers configured (that don't allow any fine + the use of the default mod_proxy's workers configured (that don't allow any fine tuning like connections reuse, etc..).

+
top
diff --git a/docs/manual/mod/mod_proxy.xml.fr b/docs/manual/mod/mod_proxy.xml.fr index ccaf2f38bd..c8c4ffa50a 100644 --- a/docs/manual/mod/mod_proxy.xml.fr +++ b/docs/manual/mod/mod_proxy.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/mod/mod_proxy.xml.ja b/docs/manual/mod/mod_proxy.xml.ja index ff6875f44e..6b4d9346c3 100644 --- a/docs/manual/mod/mod_proxy.xml.ja +++ b/docs/manual/mod/mod_proxy.xml.ja @@ -1,7 +1,7 @@ - +