Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97965 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50099 invoked from network); 25 Jan 2017 22:14:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jan 2017 22:14:21 -0000 X-Host-Fingerprint: 50.39.112.180 50-39-112-180.bvtn.or.frontiernet.net Received: from [50.39.112.180] ([50.39.112.180:29586] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/C3-00729-C3329885 for ; Wed, 25 Jan 2017 17:14:21 -0500 Message-ID: <61.C3.00729.C3329885@pb1.pair.com> To: internals@lists.php.net References: <3C5197D9-8CA8-49DB-A19F-444066CF2426@heroku.com> Date: Wed, 25 Jan 2017 14:14:17 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 50.39.112.180 Subject: Re: Fixing Apache mod_proxy_fcgi SCRIPT_FILENAME et al for good From: champion.p@gmail.com (Jacob Champion) On 01/25/2017 01:16 PM, Jacob Champion wrote: > rather than dumping yet another httpd > functional change on PHP-FPM and saying "here you go, deal with it" ("rather than *us* dumping", I should have said.) This was a confusing way for me to communicate "I don't want to just push breaking changes on you without your involvement". --Jacob