Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97964
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <AB.33.00729.BB519885@pb1.pair.com>
To: internals@lists.php.net
References: <3C5197D9-8CA8-49DB-A19F-444066CF2426@heroku.com>
Date: Wed, 25 Jan 2017 13:16:39 -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: <3C5197D9-8CA8-49DB-A19F-444066CF2426@heroku.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Fixing Apache mod_proxy_fcgi SCRIPT_FILENAME et al for good
From: champion.p@gmail.com (Jacob Champion)

On 01/17/2017 06:44 AM, David Zuelke wrote:
> What's the right place for this discussion? Would somebody with the
> right karma/experience be willing to sign up to
> https://httpd.apache.org/lists.html#http-dev and join in? Or does a
> GitHub issue or PR suffice?

Bump. I'm one of the httpd committers trying to drive this particular 
conversation -- is there anyone interested in following this from the 
PHP side?

Don't get me wrong; we have a lot to fix before you can take any final 
action, but we won't be able to turn on the new fixes at all without 
some involvement from PHP. (And it would probably be more helpful to you 
to provide feedback as we work, rather than dumping yet another httpd 
functional change on PHP-FPM and saying "here you go, deal with it".)

--Jacob