varibles set by putenv() are correctly set and visible inside programs called by exec(), passthrough(), ...

in the other hand also env vars set by SetEnv apache directive are also not available inside programs called via
exec(), passthrough(), ...

varibles set by putenv() are correctly set and visible inside programs called by exec(), passthrough(), ...

in the other hand also env vars set by SetEnv apache directive are also not available inside programs called via
exec(), passthrough(), ...

This is how Apache works and apparently PHP cannot change it.
Not PHP problem.

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

>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.

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).

Is this still relevant?

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.

You should be able to achieve this via proc_open():

Argument env:
An array with the environment variables for the command that will be run, or NULL to use the same environment as the current PHP process

I don't think it would be a great idea to enable this for exec() per default as it would change behaviour for existing scripts and possibly copying terminal variables and such which could break the scripts or introduce unwanted effects.

/Erik Lundin

Here information is given by you is too great it is very help for me thank you for this. (https://github.com.php)(https://tellpizzahut.pro/)

This post is very insightful and very informative. Thanks for sharing it. (https://github.com)(https://www.gm-socrates.com)