Re: Allowing [SAPI=] entries in ini files.

From: Date: Tue, 19 Nov 2013 18:51:30 +0000
Subject: Re: Allowing [SAPI=] entries in ini files.
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-70209@lists.php.net to get a copy of this message
2013/11/16 Richard Quadling <rquadling@gmail.com> > Hi. > > I created a patch https://github.com/php/php-src/pull/466 to > allow ini > files to have a SAPI section, just like they can have a HOST and PATH > section. > > My use case is that the provider we are currently using does not allow us > to have our own INI file, just the additional directory, and there is no > way to differentiate between a CLI and a FAST-CGI setup in the additional > directory. > > The patch allows [SAPI=xxx] sections and they operate in a very similar way > to the [HOST] and [PATH] sections. > > Please can this be considered for inclusion into PHP at some stage. > > Regards, > > Richard Quadling. > Hi, Just my 2 cents, but that sounds more like an issue with your provider/hoster and not with PHP. I always thought of the additional php.ini as a way to change some details and not a way to set up the whole runtime. Especially when a user has write access to that file it seems to me also an security issue, when PHP allows to set/change critical settings there. tl;dr: There is probably a reason, why your provider doesn't allow you to change php.ini settings directly. Regards, Sebastian -- github.com/KingCrunch

« previous php.internals (#70209) next »