Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85921
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rochette.cc designates 195.154.14.121 as permitted sender)
Message-ID: <5538E1EE.6010201@rochette.cc>
Date: Thu, 23 Apr 2015 14:13:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: multipart/alternative;
 boundary="------------020505090406010706020809"
Subject: clear_env default in php-fpm
From: mathieu@rochette.cc (Mathieu Rochette)

--------------020505090406010706020809
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

A |clear_env |settings had been added in php 5.4 with default |clear_env 
= yes| to avoid BC I imagine. With service such as heroku or with 
docker, and followinf the 12 factor principles, configuration from other 
services are defined with env vars. What do you think about changing the 
default to |clear_env = no| ? It would also match the behavior of using 
php with apache mod. Is it possible for 7.0 ? I don't know if it's too 
late for this kind of change but I guess that if it's not for 7.0 it 
would have to wait for 8.0 isn't it ?

I didn't find much information about this change (even finding about 
|clear_env| is not that easy when search for "php fpm env var") so I 
don't know if there is others reason than BC.

thank you

-- 
Mathieu Rochette


--------------020505090406010706020809--