Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70162 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67388 invoked from network); 15 Nov 2013 21:58:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Nov 2013 21:58:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.219.50 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.219.50 mail-oa0-f50.google.com Received: from [209.85.219.50] ([209.85.219.50:57076] helo=mail-oa0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EF/50-65134-B1996825 for ; Fri, 15 Nov 2013 16:58:52 -0500 Received: by mail-oa0-f50.google.com with SMTP id k1so4599266oag.23 for ; Fri, 15 Nov 2013 13:58:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=ZAU9HUxZRtAWjQA5Hijhnzd5lm8Rv7IIcvjTkee97a4=; b=Bf0g+U6VOotm3KRECGSUnA+dJkHkkQ4iiQlwUCiYgWpZBXe6qGZHN1XHQ8jPG42U5X qQQ1i5Es4U7mobEca3zXucjqnyoicsmq8BrH5AaW0KjHLM/JeIO2KNfkak46HEW3HgWt s/21GagROgt4pqk0MaR3fVP6RH5hEMtvFQM2s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=ZAU9HUxZRtAWjQA5Hijhnzd5lm8Rv7IIcvjTkee97a4=; b=SnireBGvxAChUbzbIN1AkC81tb11t3+qfg49Oj4CxT8H9cv7HAsP4Zmi3e1kf6vTdF VD+42A+pose0QX544LSA8V3FQHmIgoOUhvuKpj/ql2+f6Jy+N7WPI6aKzJBs3CkkegWR FdGwM8yKDwIowToUHAuOWkznscx7Nhkmo1hpoSj7dZLxswz/naey+LwqDvqQ6ZMYoq6w a4gUbmLra3MWWVkNeMb0qUHiiqUEFs2kXAF9QZUYZhq4C29m4zsk+GcKuCVIjXtxsk57 /Hi0wnoYPwSofNw71vcMZTlHc61qVvwt7goHcYQEz8sV4AuAEQP4FOdXtLzyYLVv7ve8 qvOw== X-Gm-Message-State: ALoCoQkvlMWB+oFQ2Dxe+7ker47cA2DlocxYOP3tz5sAAn8YLA+gpWYohHfWdRVUZ2ET5C6p5lJW X-Received: by 10.182.92.138 with SMTP id cm10mr2710083obb.95.1384552728858; Fri, 15 Nov 2013 13:58:48 -0800 (PST) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.76.178.161 with HTTP; Fri, 15 Nov 2013 13:58:28 -0800 (PST) In-Reply-To: References: Date: Fri, 15 Nov 2013 13:58:28 -0800 X-Google-Sender-Auth: 5g1jQZ7Vg7t83zSOlqRx0-cRYhk Message-ID: To: Ferenc Kovacs Cc: Michael Wallner , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] PHP-5.6 and $HTTP_RAW_POST_DATA From: aharvey@php.net (Adam Harvey) On 15 November 2013 13:34, Ferenc Kovacs wrote: > On Fri, Nov 15, 2013 at 8:18 AM, Michael Wallner wrote: >> >> 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. > > From my understanding, reintroducing always_populate_raw_post_data would > still not guarantee 100% BC, as in most cases $HTTP_RAW_POST_DATA would > still be populated previously without the need of setting > always_populate_raw_post_data=1. That's my understanding too. > I would also like to hear what others think about this. Bottom line: I don't think we should break BC in a minor release. Yes, the API sucks, and hopefully people are already using php://input consistently, but for the sake of one global I don't think we should break people's code until we increment the major number. Adam