hi, That was one other thing related to this addition, not specifically the main reason why I think this addition is not as good as expected. Especially as as Gustavo said as well, it is possible to do it using a nice and clean APIs instead of adding yet another cryptic ini setting.
I'm not saying that there is no need to improve what this feature does but adding yet another option to deal with HTTP input is somehow very bad. On Sat, Dec 18, 2010 at 6:06 PM, Daniel Convissor <dani...@analysisandsolutions.com> wrote: > Hi Pierre: > > On Thu, Dec 16, 2010 at 01:32:15PM +0100, Pierre Joye wrote: > >> However I would >> prefer to bring back a proposal we had a couple of years ago, to >> totally disable post data. > > Completely disabling POST is something that is probably best done > via web server configurations. Doing this at the > applicaiton/programming layer seems like a kludge. > > --Dan > > -- > T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y > data intensive web and database programming > http://www.AnalysisAndSolutions.com/ > 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
