Req #37989 [Fbk->Opn]: Enviroment variables not availabe on exec,mail,...

Edit report at https://bugs.php.net/bug.php?id=37989&edit=1 ID: 37989 User updated by: david at ols dot es Reported by: david at ols dot es Summary: Enviroment variables not availabe on exec,mail,... -Status: Feedback +Status: Open Type: Feature/Change Request Package: *General Issues Operating System: Linux PHP Version: 4.4.2 Block user comment: N Private report: N New Comment: yes, as an exmaple, having the REMOTE_ADDR user ip address will be very helpful when calling mail so the mailer could check it against spamhaus/cbl , also having REQUEST_URI available could help tracking problems in an enviroment where one has control over the mailer but not over the customer php scripts, specially when the website has been compromised or infected by malware. Will be really useful to track and limit the damage caused in such situations. Previous Comments: ------------------------------------------------------------------------ [2017-01-20 21:06:45] heiglandreas@php.net Is this still relevant? ------------------------------------------------------------------------ [2015-12-08 12:49:03] david at ols dot es Related To: Bug #36341 ------------------------------------------------------------------------ [2006-07-03 07:42:54] david at ols dot es ok, but according to apache documentation apache setenv "Sets an environment variable, which is then passed on to CGI scripts and SSI pages" , it could be considered that those variables should also be in php enviroment, where in fact they appear to be (as they could be accesed with getenv) and that it should also be in the enviroment of programs called by php. From a strict point of view the enviroment of apache should be propagated to php and then also to programs called by php. Apache API has functions to initialize and set the enviroment but that functions are not called by the php module. In th other hand when php is run as cgi then that enviroment is correctly set which makes it more inconsistent with how it works when run as an apache module. Maybe this could be trated as a feature request rather than an bug (and i could provide a patch for the apache php module which will correctly set the enviroment). Anyway the documentation should be changed to state that the apache enviroment in not really in the real program enviroment and that is not available for programs called by php). ------------------------------------------------------------------------ [2006-07-03 06:47:28] tony2001@php.net >If PHP can access that variables via getenv() it (should) >mean that they are in the enviroment Nope. That means only that those "environment" variables are in Apache hash. ------------------------------------------------------------------------ [2006-07-03 05:57:51] david at ols dot es If PHP can access that variables via getenv() it (should) mean that they are in the enviroment and should also be accesible to programs called by PHP, but they are not. This does not look like a apache issue, it's PHP who calls the external programs and who has the chance to set it's enviroment ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=37989 -- Edit this bug report at https://bugs.php.net/bug.php?id=37989&edit=1