Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70190
Return-Path: <julienpauli@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 42580 invoked from network); 18 Nov 2013 13:34:37 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 18 Nov 2013 13:34:37 -0000
Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.53 as permitted sender)
X-PHP-List-Original-Sender: julienpauli@gmail.com
X-Host-Fingerprint: 209.85.212.53 mail-vb0-f53.google.com  
Received: from [209.85.212.53] ([209.85.212.53:45398] helo=mail-vb0-f53.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 79/30-41213-C671A825 for <internals@lists.php.net>; Mon, 18 Nov 2013 08:34:37 -0500
Received: by mail-vb0-f53.google.com with SMTP id g10so498437vbg.12
        for <internals@lists.php.net>; Mon, 18 Nov 2013 05:34:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type;
        bh=7hju2FUZw1/wEZ2PkGzNlKxoQ+iC0gyPxErPcbeRyJk=;
        b=Fw7etkrbqsNTIKPi+Ghbvg6A+3LGTeC3FYBcPexT9qASn6XJ7GufwFi3dZK3X3upPJ
         Pq5ORvqCMLlqfyDdEt9puWaK73vA/jHWtj8jFyDjaTS98cwV/py/9HB4bV5SAudASaPI
         RPSaq4bJew5MbZ0ig2Gqbovl4pa8rvcGAtsR2t4WRqKah76R8gkCKs3lZsr8MdV33X2Q
         wQ9cx17rcxkT3W5ZiJ0u9FW7dLAXHjZlNfl764VjEK3wJzRYXNGzh9DmnSsO7X0uzYgl
         fSyN6ttOLsJyISPvwpNDs767EDU9CnDywqVqXeBRdxPXTCKY+28VBep5L49aLDwgB4yn
         UFaA==
X-Received: by 10.58.207.15 with SMTP id ls15mr15671349vec.17.1384781673843;
 Mon, 18 Nov 2013 05:34:33 -0800 (PST)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
Received: by 10.220.73.197 with HTTP; Mon, 18 Nov 2013 05:33:52 -0800 (PST)
In-Reply-To: <CAH-PCH7z9WEsb661nRNVEVJKW+uXWPb-mjgwBUHx1Ee0Oipmvw@mail.gmail.com>
References: <A0.00.16321.7BAC5825@pb1.pair.com> <CAGa2bXaoWhuFar6H=CY0zk1Boixc9CwiLesmKj1_iNC96MvFWA@mail.gmail.com>
 <CAH-PCH6HCphCyTg9FAbxznn9RFkFfgFC-0LeuRUmFHvp=H=rgw@mail.gmail.com>
 <CADajX4AYQxOaRGWGxgUU36zPibJ4DKkkFvS+8TdAY5UZ11m+_w@mail.gmail.com>
 <CAGa2bXZQWjPSQgQOai5wKsDsmAyegMSHPq4z+zPSSi5EPYNSKQ@mail.gmail.com> <CAH-PCH7z9WEsb661nRNVEVJKW+uXWPb-mjgwBUHx1Ee0Oipmvw@mail.gmail.com>
Date: Mon, 18 Nov 2013 14:33:52 +0100
X-Google-Sender-Auth: mer-7mCmTUrNh-9zYQ_fRx5i3jE
Message-ID: <CAMUwpuS+R+Y3vxa-hK2Cy+zJhVaKX2_bFMm7n3-PWQqk1rRjLA@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: Yasuo Ohgaki <yohgaki@ohgaki.net>, Adam Harvey <aharvey@php.net>, Michael Wallner <mike@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b6dc6eec2d15904eb739b47
Subject: Re: [PHP-DEV] PHP-5.6 and $HTTP_RAW_POST_DATA
From: jpauli@php.net (Julien Pauli)

--047d7b6dc6eec2d15904eb739b47
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Nov 16, 2013 at 12:13 AM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

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

Please, remember that our release process forbidds BC breaks.

I suggest reintroducing the feature, together with
always_populate_raw_post_data (like the old behavior).

Thanks.

Julien

--047d7b6dc6eec2d15904eb739b47--