You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by po...@apache.org on 2010/02/05 03:48:34 UTC
svn commit: r906779 - /httpd/httpd/trunk/docs/manual/configuring.xml
Author: poirier
Date: Fri Feb 5 02:48:34 2010
New Revision: 906779
URL: http://svn.apache.org/viewvc?rev=906779&view=rev
Log:
Be specific about which environment variables can be used in
expansions in the server configuration file.
Modified:
httpd/httpd/trunk/docs/manual/configuring.xml
Modified: httpd/httpd/trunk/docs/manual/configuring.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/configuring.xml?rev=906779&r1=906778&r2=906779&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/configuring.xml (original)
+++ httpd/httpd/trunk/docs/manual/configuring.xml Fri Feb 5 02:48:34 2010
@@ -87,6 +87,12 @@
unchanged for use by later stages in the config file
processing.)</p>
+ <p>Only environment variables defined before the server is started
+ can be used in expansions. Variables defined in the
+ configuration file itself, for example with <directive
+ module="mod_env">SetEnv</directive>, take effect too late to be
+ used for expansions in the configuration file.</p>
+
<p>The maximum length of a line in the configuration file, after
environment-variable substitution, joining any continued lines and
removing leading and trailing white space, is 8192 characters.</p>
Re: svn commit: r906779 - /httpd/httpd/trunk/docs/manual/configuring.xml
Posted by Jeff Trawick <tr...@gmail.com>.
On Fri, Feb 5, 2010 at 7:51 AM, Dan Poirier <po...@pobox.com> wrote:
> [Moving discussion from dev@ to docs@httpd.apache.org]
>
> On Fri, Feb 5, 2010, at 06:57:58 AM, Jeff Trawick <tr...@gmail.com> wrote:
>
>> On Thu, Feb 4, 2010 at 9:48 PM, <po...@apache.org> wrote:
>>> + <p>Only environment variables defined before the server is started
>>> + can be used in expansions. Variables defined in the
>>> + configuration file itself, for example with <directive
>>> + module="mod_env">SetEnv</directive>, take effect too late to be
>>> + used for expansions in the configuration file.</p>
>>
>> I think the "take effect too late..." wording supports the common
>> confusion that OS-level environment variables and those server
>> variables that are set in the environment of sub-processes are
>> essentially the same thing.
>>
>> I don't know what the magic distinguishing words are. Perhaps "OS
>> environment variable," with a link to a new glossary entry, should be
>> used in the appropriate places? The glossary entry for Environment
>> variable describes the difference but doesn't introduce unique
>> terminology for the two types of variables
>> (http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable.
>
> I agree that it's still ambiguous or even misleading. I played with
> trying to expand on that, but couldn't come up with wording I liked last
> night.
>
> It would definitely help to have unique terminology. Maybe "operating
> system environment variables" for the ones set outside the server in the
> OS, and "server environment variables" for the ones set inside the
> server? There's still some possible confusion because the "server"
> variables become operating system environment variables for CGI scripts,
> though.
>
> If we can find consensus on terminology, I'll update the glossary and
> the env page <http://httpd.apache.org/docs/trunk/env.html>, and try to
> find and disambiguate as many references as I can find and link back to
> the glossary.
Cool... I'm happy to help given some additional advice from the crowd.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r906779 -
/httpd/httpd/trunk/docs/manual/configuring.xml
Posted by Dan Poirier <po...@pobox.com>.
[Moving discussion from dev@ to docs@httpd.apache.org]
On Fri, Feb 5, 2010, at 06:57:58 AM, Jeff Trawick <tr...@gmail.com> wrote:
> On Thu, Feb 4, 2010 at 9:48 PM, <po...@apache.org> wrote:
>> + <p>Only environment variables defined before the server is started
>> + can be used in expansions. Variables defined in the
>> + configuration file itself, for example with <directive
>> + module="mod_env">SetEnv</directive>, take effect too late to be
>> + used for expansions in the configuration file.</p>
>
> I think the "take effect too late..." wording supports the common
> confusion that OS-level environment variables and those server
> variables that are set in the environment of sub-processes are
> essentially the same thing.
>
> I don't know what the magic distinguishing words are. Perhaps "OS
> environment variable," with a link to a new glossary entry, should be
> used in the appropriate places? The glossary entry for Environment
> variable describes the difference but doesn't introduce unique
> terminology for the two types of variables
> (http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable.
I agree that it's still ambiguous or even misleading. I played with
trying to expand on that, but couldn't come up with wording I liked last
night.
It would definitely help to have unique terminology. Maybe "operating
system environment variables" for the ones set outside the server in the
OS, and "server environment variables" for the ones set inside the
server? There's still some possible confusion because the "server"
variables become operating system environment variables for CGI scripts,
though.
If we can find consensus on terminology, I'll update the glossary and
the env page <http://httpd.apache.org/docs/trunk/env.html>, and try to
find and disambiguate as many references as I can find and link back to
the glossary.
Dan
Re: svn commit: r906779 -
/httpd/httpd/trunk/docs/manual/configuring.xml
Posted by Dan Poirier <po...@pobox.com>.
[Moving discussion from dev@ to docs@httpd.apache.org]
On Fri, Feb 5, 2010, at 06:57:58 AM, Jeff Trawick <tr...@gmail.com> wrote:
> On Thu, Feb 4, 2010 at 9:48 PM, <po...@apache.org> wrote:
>> + <p>Only environment variables defined before the server is started
>> + can be used in expansions. Variables defined in the
>> + configuration file itself, for example with <directive
>> + module="mod_env">SetEnv</directive>, take effect too late to be
>> + used for expansions in the configuration file.</p>
>
> I think the "take effect too late..." wording supports the common
> confusion that OS-level environment variables and those server
> variables that are set in the environment of sub-processes are
> essentially the same thing.
>
> I don't know what the magic distinguishing words are. Perhaps "OS
> environment variable," with a link to a new glossary entry, should be
> used in the appropriate places? The glossary entry for Environment
> variable describes the difference but doesn't introduce unique
> terminology for the two types of variables
> (http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable.
I agree that it's still ambiguous or even misleading. I played with
trying to expand on that, but couldn't come up with wording I liked last
night.
It would definitely help to have unique terminology. Maybe "operating
system environment variables" for the ones set outside the server in the
OS, and "server environment variables" for the ones set inside the
server? There's still some possible confusion because the "server"
variables become operating system environment variables for CGI scripts,
though.
If we can find consensus on terminology, I'll update the glossary and
the env page <http://httpd.apache.org/docs/trunk/env.html>, and try to
find and disambiguate as many references as I can find and link back to
the glossary.
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org
Re: svn commit: r906779 - /httpd/httpd/trunk/docs/manual/configuring.xml
Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Feb 4, 2010 at 9:48 PM, <po...@apache.org> wrote:
> Author: poirier
> Date: Fri Feb 5 02:48:34 2010
> New Revision: 906779
>
> URL: http://svn.apache.org/viewvc?rev=906779&view=rev
> Log:
> Be specific about which environment variables can be used in
> expansions in the server configuration file.
>
> Modified:
> httpd/httpd/trunk/docs/manual/configuring.xml
>
> Modified: httpd/httpd/trunk/docs/manual/configuring.xml
> URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/configuring.xml?rev=906779&r1=906778&r2=906779&view=diff
> ==============================================================================
> --- httpd/httpd/trunk/docs/manual/configuring.xml (original)
> +++ httpd/httpd/trunk/docs/manual/configuring.xml Fri Feb 5 02:48:34 2010
> @@ -87,6 +87,12 @@
> unchanged for use by later stages in the config file
> processing.)</p>
>
> + <p>Only environment variables defined before the server is started
> + can be used in expansions. Variables defined in the
> + configuration file itself, for example with <directive
> + module="mod_env">SetEnv</directive>, take effect too late to be
> + used for expansions in the configuration file.</p>
I think the "take effect too late..." wording supports the common
confusion that OS-level environment variables and those server
variables that are set in the environment of sub-processes are
essentially the same thing.
I don't know what the magic distinguishing words are. Perhaps "OS
environment variable," with a link to a new glossary entry, should be
used in the appropriate places? The glossary entry for Environment
variable describes the difference but doesn't introduce unique
terminology for the two types of variables
(http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable.
Make sense?
Re: svn commit: r906779 - /httpd/httpd/trunk/docs/manual/configuring.xml
Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Feb 4, 2010 at 9:48 PM, <po...@apache.org> wrote:
> Author: poirier
> Date: Fri Feb 5 02:48:34 2010
> New Revision: 906779
>
> URL: http://svn.apache.org/viewvc?rev=906779&view=rev
> Log:
> Be specific about which environment variables can be used in
> expansions in the server configuration file.
>
> Modified:
> httpd/httpd/trunk/docs/manual/configuring.xml
>
> Modified: httpd/httpd/trunk/docs/manual/configuring.xml
> URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/configuring.xml?rev=906779&r1=906778&r2=906779&view=diff
> ==============================================================================
> --- httpd/httpd/trunk/docs/manual/configuring.xml (original)
> +++ httpd/httpd/trunk/docs/manual/configuring.xml Fri Feb 5 02:48:34 2010
> @@ -87,6 +87,12 @@
> unchanged for use by later stages in the config file
> processing.)</p>
>
> + <p>Only environment variables defined before the server is started
> + can be used in expansions. Variables defined in the
> + configuration file itself, for example with <directive
> + module="mod_env">SetEnv</directive>, take effect too late to be
> + used for expansions in the configuration file.</p>
I think the "take effect too late..." wording supports the common
confusion that OS-level environment variables and those server
variables that are set in the environment of sub-processes are
essentially the same thing.
I don't know what the magic distinguishing words are. Perhaps "OS
environment variable," with a link to a new glossary entry, should be
used in the appropriate places? The glossary entry for Environment
variable describes the difference but doesn't introduce unique
terminology for the two types of variables
(http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable.
Make sense?
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org