From: Rich Bowen
The values of variables defined with the
- Define of or shell environment variables can be used in
- configuration file lines using the syntax ${VAR}.
- If "VAR" is the name of a valid variable, the value
- of that variable is substituted into that spot in the
- configuration file line, and processing continues as if that text
- were found directly in the configuration file. Variables defined with
- Define take precedence over shell
- environment variables. If the "VAR" variable is not found, the characters
- ${VAR} are left unchanged, and a warning is logged. Variable
- names may not contain colon ":" characters, to avoid clashes with
+
The values of variables defined with the Define of or shell environment variables can
+ be used in configuration file lines using the syntax ${VAR}.
+ If "VAR" is the name of a valid variable, the value of that variable is
+ substituted into that spot in the configuration file line, and processing
+ continues as if that text were found directly in the configuration file.
+ Variables defined with Define take
+ precedence over shell environment variables.
+ If the "VAR" variable is not found, the characters ${VAR}
+ are left unchanged, and a warning is logged.
+ Variable names may not contain colon ":" characters, to avoid clashes with
RewriteMap's syntax.
Only shell environment variables defined before the server is started
can be used in expansions. Environment variables defined in the
- configuration file itself, for example with
- SetEnv, take effect too late to be used for expansions in the
- configuration file.
SetEnv, take effect too late to be used for
+ expansions in the configuration file.
The maximum length of a line in the configuration file, after variable substitution, joining any continued lines and removing leading diff --git a/docs/manual/configuring.xml.de b/docs/manual/configuring.xml.de index 00373fce212..c2cf0faf956 100644 --- a/docs/manual/configuring.xml.de +++ b/docs/manual/configuring.xml.de @@ -1,7 +1,7 @@ - + + + + + + +