Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70163
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <A0.00.16321.7BAC5825@pb1.pair.com>
References: <A0.00.16321.7BAC5825@pb1.pair.com>
Date: Sat, 16 Nov 2013 07:01:23 +0900
Message-ID: <CAGa2bXaoWhuFar6H=CY0zk1Boixc9CwiLesmKj1_iNC96MvFWA@mail.gmail.com>
To: Michael Wallner <mike@php.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c259ae28555404eb3e59ce
Subject: Re: [PHP-DEV] PHP-5.6 and $HTTP_RAW_POST_DATA
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c259ae28555404eb3e59ce
Content-Type: text/plain; charset=UTF-8

Hi Mike,

On Fri, Nov 15, 2013 at 4:18 PM, Michael Wallner <mike@php.net> wrote:

> Hi there!
>
> There seem to be concerns about the removal of $HTTP_RAW_POST_DATA in
> PHP-5.6. Nobody mentioned it would be an unacceptable BC break in the
> discussions of the POST data temp stream feature, so I was a bit
> surprised when it came up.
>
> Anyway, what's the opnion on that? For me it is a non-issue, because BC
> can be restored with one line ($GLOBALS["HTTP_RAW_POST_DATA"] =
> file_get_contents("php://input")).
> But I could probably re-add the always_populate_raw_post_data INI setting
> and do more or less what the one-liner does internally.
>
> Thoughts?
>

How about create $HTTP_RAW_POST_DATA on demand?
Just like $_ENV.

Personally, I don't mind this BC break at all as it is simple to workaround.
We can have RFC vote from now.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c259ae28555404eb3e59ce--