Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70199
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender)
Message-ID: <528B3C03.5090804@gmail.com>
Date: Tue, 19 Nov 2013 14:22:59 +0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Michael Wallner <mike@php.net>, 
 PHP internals <internals@lists.php.net>
References: <CALJZF3hPY01c9EoVg3HYZec8TzuKwNkxZQvE58mtwh-WouUJfQ@mail.gmail.com>
In-Reply-To: <CALJZF3hPY01c9EoVg3HYZec8TzuKwNkxZQvE58mtwh-WouUJfQ@mail.gmail.com>
OpenPGP: id=1D219F11
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="HmJSkDRd16pX7c8PfFechao7WWIjIDWpJ"
Subject: Re: [PHP-DEV] [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA)
From: indeyets@gmail.com (Alexey Zakhlestin)

--HmJSkDRd16pX7c8PfFechao7WWIjIDWpJ
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 19.11.13, 13:46, Michael Wallner wrote:
> On 19 November 2013 02:38, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>> Hi Julien,
>>
>> On Mon, Nov 18, 2013 at 10:33 PM, Julien Pauli <jpauli@php.net> wrote:=

>>>
>>> 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).
>>
>>
>> What we need is vote for the change?
>>
>> Mike, could you prepare RFC whether we keep the ini setting or just us=
e
>> "input://".
>> I think it's time to vote.
>=20
> Here you go, https://wiki.php.net/rfc/slim_post_data
> Though, with only two supporters, chances are low.

We can't break BC in 5.x, so the way to go is:

1. implement underlying changes
2. restore backwards compatibility (HTTP_RAW_POST_DATA should be
auto-populated in all cases when it is populated now)
3. always_populate_raw_post_data should be introduced for BC purposes

4. Is it possible to detect usage of HTTP_RAW_POST_DATA and give
E_DEPRECATED while doing so?

5. remove HTTP_RAW_POST_DATA support in master (thinking about 6.x)

--=20
Alexey Zakhlestin
CTO at Grids.by/you
https://github.com/indeyets
PGP key: http://indeyets.ru/alexey.zakhlestin.pgp.asc


--HmJSkDRd16pX7c8PfFechao7WWIjIDWpJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJSizwMAAoJEMkJcRxZdR27qJsH/ixmApb04DRcHG1VXIuFBmDa
CGxkAtWOmXfvUSO1+dGjwAAvYR8wkcwokN8H8a885JNa6c0CrGWC+T36mmSpplW+
j+ruU0khnzJdY9Uuzks+JaZkGIP9kpEjqqwyTGqI5seq965I7EReNpqFgHdNiljo
nDCI1RV+4gz4k5bQ8roCaJl+ZDgPqFDQXoxJ0IJ9elKKNHUyVzFgw6xepp4QYSDr
Q4cX3MEocal3dp2lygFCNAkde89lLiv4tjijtvLimyT9npxGnS6y2qSNoX8Fcdfa
5h1oVq9Vmg3Rc0+QG+PnzQDdThDdPB+Aw1Jzdo/Z9rEHVEi2bnIMQBk3lLV67yk=
=AJeV
-----END PGP SIGNATURE-----

--HmJSkDRd16pX7c8PfFechao7WWIjIDWpJ--