Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70206 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23424 invoked from network); 19 Nov 2013 12:52:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Nov 2013 12:52:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=arvids.godjuks@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=arvids.godjuks@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.180 as permitted sender) X-PHP-List-Original-Sender: arvids.godjuks@gmail.com X-Host-Fingerprint: 209.85.217.180 mail-lb0-f180.google.com Received: from [209.85.217.180] ([209.85.217.180:62483] helo=mail-lb0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E2/81-15197-F1F5B825 for ; Tue, 19 Nov 2013 07:52:48 -0500 Received: by mail-lb0-f180.google.com with SMTP id w6so2487906lbh.25 for ; Tue, 19 Nov 2013 04:52:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=QRxOLKXpFXi5kQrIZKQ6Jh5y3RxVFWN9stWhBwresag=; b=WakzwbPwcg/oASlzlcST5C7GNXWFDFYh1xOas8GSjXqsW37xm16/Sy0T4TxotSZEhP 2IYMRqCfoulxYpz8FjJNCc+OUho/9aImAvP499+X4qk9DGPKV1pdrhnrQYY+8dHRanKX rImnhbpk90CT5sfBukAcs96TD20qhezLTICsPX6OnJMDpgBBoZZI3De+TmGUONy63Ws6 MN/pcezFavIZ6wT1pACBeHh8y7rKx/FJDX+6iT7uOEfvkhP5oMJf3mrfq5fKgRoJCBjS JfJytPkh0TvNCAQSpJz/DGE7hyQUsmRa9LgzIXx487UaYHPTwFY/eSZE4WTH937P/fzk dkIA== X-Received: by 10.152.203.129 with SMTP id kq1mr8432lac.77.1384865563795; Tue, 19 Nov 2013 04:52:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.3.200 with HTTP; Tue, 19 Nov 2013 04:52:23 -0800 (PST) In-Reply-To: <528B5D81.7020506@gmail.com> References: <528B3C03.5090804@gmail.com> <528B5221.5050502@gmail.com> <528B5D81.7020506@gmail.com> Date: Tue, 19 Nov 2013 14:52:23 +0200 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary=001a113480a0fde6d404eb872310 Subject: Re: [PHP-DEV] [RFC] Slim POST data (was: PHP-5.6 and $HTTP_RAW_POST_DATA) From: arvids.godjuks@gmail.com (Arvids Godjuks) --001a113480a0fde6d404eb872310 Content-Type: text/plain; charset=UTF-8 2013/11/19 Alexey Zakhlestin > 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. --001a113480a0fde6d404eb872310--