Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70151 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16370 invoked from network); 15 Nov 2013 07:18:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Nov 2013 07:18:16 -0000 X-Host-Fingerprint: 178.18.170.101 178-18-170-101.customer.bnet.at Date: Fri, 15 Nov 2013 02:18:15 -0500 Received: from [178.18.170.101] ([178.18.170.101:2598] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A0/00-16321-7BAC5825 for ; Fri, 15 Nov 2013 02:18:15 -0500 Message-ID: To: internals@lists.php.net User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Posted-By: 178.18.170.101 Subject: PHP-5.6 and $HTTP_RAW_POST_DATA From: mike@php.net (Michael Wallner) 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?