Re: PHP-5.6 and $HTTP_RAW_POST_DATA

From: Date: Fri, 15 Nov 2013 23:13:18 +0000
Subject: Re: PHP-5.6 and $HTTP_RAW_POST_DATA
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-70168@lists.php.net to get a copy of this message
On Fri, Nov 15, 2013 at 11:49 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote: > Hi all, > > On Sat, Nov 16, 2013 at 7:19 AM, Adam Harvey <aharvey@php.net> wrote: > >> On 15 November 2013 14:14, Ferenc Kovacs <tyra3l@gmail.com> wrote: >> > On Fri, Nov 15, 2013 at 11:01 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> >> wrote: >> >> How about create $HTTP_RAW_POST_DATA on demand? >> >> Just like $_ENV. >> > >> > if you do that don't forget to update the opcode caches(opcache, apc, >> etc.) >> > also, I remember it caused them problems when we >> > introduced auto_globals_jit. >> >> If that is feasible, do we also want to consider emitting an >> E_DEPRECATED on first access? > > > Good idea. > > Another option is initialize $HTTP_RAW_POST_DATA when > > always_populate_raw_post_data = On > that was the suggestion from Michael in his opening mail. and I replied to that already (it is a workaround to bring back the old behavior, but doesn't entirely resolve the bc issue). > > It would be simpler than JIT. > I prefer current implementation, though. > +1 for going simple -- Ferenc Kovács @Tyr43l - http://tyrael.hu

« previous php.internals (#70168) next »