Re: [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA)
| From: | Arvids Godjuks | Date: | Tue, 19 Nov 2013 12:52:23 +0000 |
| Subject: | Re: [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA) | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-70206@lists.php.net to get a copy of this message | ||
2013/11/19 Alexey Zakhlestin <indeyets@gmail.com>
> On 19.11.13, 16:32, Arvids Godjuks wrote:
>
> > My take on it is just to leave the always_populate_raw_post_data in
> place,
> > because it is Off by default already.
>
> That's not enough. As far as I understand, even when this option is set
> to "Off", HTTP_RAW_POST_DATA would be populated for unknown mime-types
>
> see
>
>
> http://docs.php.net/manual/en/ini.core.php#ini.always-populate-raw-post-data
>
--
> Alexey Zakhlestin
> CTO at Grids.by/you
> https://github.com/indeyets
> PGP key: http://indeyets.ru/alexey.zakhlestin.pgp.asc
>
Doh, not careful enough reading is to blame :)
Then I see 2 ways of doing it:
1. Adding just the deprecation warnings.
2. Besides the warnings, add a new valid value for
always-populate-raw-post-data - "fully_disabled" or just
"disabled"|"disable" to completely turn it off, so people can actually test
how their apps will behave.
Arvids.