>Number: 4234
>Category: mod_env
>Synopsis: mod_env directives not availible from .htaccess
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: change-request
>Submitter-Id: apache
>Arrival-Date: Mon Apr 12 12:00:02 PDT 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.6
>Environment:
All
>Description:
It would be good to have access to the mod_env directives (SetEnv, etc.) from
the .htaccess file. Currently, they can only be used in the *.conf files.
Making these availible in .htaccess would help those of us who have our sites
hosted on machines where we do not control the *.conf files.
For example, PHP requires that the TMPDIR envirionment variable be set outside
of a script for file uploads (PUT) to work. This makes uploads impossible with
PHP -- unless I can get this change implemented (My IPP will be more comfortable
installing a new version of Apache than patching their installation with my
patches.)
>How-To-Repeat:
Put a SetEnv directive in the .htaccess file. Watch the error log when
a file in that directory is accessed.
>Fix:
--- mod_env.c.orig Mon Mar 22 17:38:21 1999
+++ mod_env.c Mon Apr 12 12:49:19 1999
@@ -226,11 +226,11 @@
static const command_rec env_module_cmds[] =
{
{"PassEnv", add_env_module_vars_passed, NULL,
- RSRC_CONF, RAW_ARGS, "a list of environment variables to pass to CGI."},
+ OR_OPTIONS, RAW_ARGS, "a list of environment variables to pass to CGI."},
{"SetEnv", add_env_module_vars_set, NULL,
- RSRC_CONF, RAW_ARGS, "an environment variable name and a value to pass to
CGI."},
+ OR_OPTIONS, RAW_ARGS, "an environment variable name and a value to pass
to CGI."},
{"UnsetEnv", add_env_module_vars_unset, NULL,
- RSRC_CONF, RAW_ARGS, "a list of variables to remove from the CGI
environment."},
+ OR_OPTIONS, RAW_ARGS, "a list of variables to remove from the CGI
environment."},
{NULL},
};
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]
