www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject Re: mod_env/4856: UnsetEnv does not actually Unset the Env
Date Fri, 13 Aug 1999 09:20:18 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> 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!     ]


Synopsis: UnsetEnv does not actually Unset the Env

Comment-Added-By: coar
Comment-Added-When: Fri Aug 13 02:20:17 PDT 1999
Comment-Added:

Some environment variables are *required* by the CGI
spec.  SERVER_NAME is one of these.  See the description
at <http://Web.Golux.com/coar/cgi/draft-coar-cgi-v11-03-clean.html#6.1.15>.
If your claim is that UnsetEnv doesn't work for *any*
envariable in a CGI environment, that's a legitimate bug --
but SERVER_NAME is not a good example. :-)

Synopsis-Changed-From: UnsetEnv does not actually Unset the Env
Synopsis-Changed-To: Not all environment variables can be unset with UnsetEnv
Synopsis-Changed-By: coar
Synopsis-Changed-When: Fri Aug 13 02:20:17 PDT 1999
Release-Changed-From-To: 1.3.6 Win32-1.3.6
Release-Changed-By: coar
Release-Changed-When: Fri Aug 13 02:20:17 PDT 1999


Mime
View raw message