From: Luca Toscano
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:
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.
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..).