>Number: 4856
>Category: mod_env
>Synopsis: UnsetEnv does not actually Unset the Env
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Thu Aug 12 20:20:00 PDT 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.6 Win32
>Environment:
Intel NT 4 0 1381 Service Pack 5
>Description:
When attempting to use the UnsetEnv directive, which the docs say "Removes one
or more environment variables from those passed on to CGI scripts."
However, the ENV variable that I try to remove is still being passed to the the
CGI program.
This is distinctly non-critical, but something that I observed while tinkering
with my config files.
>How-To-Repeat:
In httpd.conf, put the line:
UnsetEnv SERVER_NAME
or similar. Then run a CGI program that dumps the environment variables, such
as:
#!/usr/bin/perl
print "Content-type: text/html\n\n";
for(keys%ENV){print"$_ => $ENV{$_}<br>\n";}
The environment variable specified (SERVER_NAME) is still being supplied to the
CGI.
>Fix:
>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 make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database 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! ]
