Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97810
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.49 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <3C5197D9-8CA8-49DB-A19F-444066CF2426@heroku.com>
Date: Tue, 17 Jan 2017 15:44:34 +0100
To: PHP internals list <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Fixing Apache mod_proxy_fcgi SCRIPT_FILENAME et al for good
From: dz@heroku.com (David Zuelke)

Hi all,

https://github.com/php/php-src/pull/694 and =
https://github.com/php/php-src/pull/765 brought support for Apache's =
"SetHandler" based mod_proxy_fcgi-to-FPM interface.

Recently, a change in Apache =
(https://github.com/apache/httpd/commit/cab0bfbb2645bb8f689535e5e2834e2dbc=
23f5a5) broke this again, so FPM no longer works with Apache 2.4.23 and =
later.

The HTTPD developers are interested in fixing this once and for all, by =
cleaning up several inconsistencies on their side in one go. However, =
that would require accompanying changes on the PHP side in all of the =
FPM and FCGI SAPI's detection logic, and that needs coordinating :)

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?

David

P.S. obviously, the 5.6 active support EOL timing isn't ideal for such a =
change, but we can cross that bridge when we get there ;)