ask 2002/06/04 03:01:49
Modified: src/docs/2.0/user/config config.pod
Log:
SetupEnv is "PerlOptions"; not "Options".
Revision Changes Path
1.14 +4 -4 modperl-docs/src/docs/2.0/user/config/config.pod
Index: config.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/config/config.pod,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- config.pod 2 Jun 2002 13:43:23 -0000 1.13
+++ config.pod 4 Jun 2002 10:01:49 -0000 1.14
@@ -246,7 +246,7 @@
But C<%ENV> population is expensive. Those who have moved to the Perl
Apache API no longer need this extra C<%ENV> population, and can gain
by disabling it. A code using the C<CGI.pm> module require
-C<PerlSetupEnv On> because that module relies on a properly populated
+C<PerlOptions +SetupEnv> because that module relies on a properly populated
CGI environment table.
This option is enabled by default for sections configured as:
@@ -261,13 +261,13 @@
<Location ...>
SetHandler perl-script
- Options -SetupEnv
+ PerlOptions -SetupEnv
...
</Location>
or globally:
- Options -SetupEnv
+ PerlOptions -SetupEnv
<Location ...>
...
</Location>
@@ -278,7 +278,7 @@
When this option is disabled you can still read environment variables
set by you. For example when you use the following configuration:
- Options -SetupEnv
+ PerlOptions -SetupEnv
PerlModule Modperl::Registry
<Location /perl>
PerlSetEnv TEST hi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
