Ahh... thanks! Yeah, it looks like other than removing the
prefix (and host:port), it does nothing more Apache-wise.
> On Jan 27, 2017, at 8:28 AM, Luca Toscano <toscano.l...@gmail.com> wrote:
>
>
>
> 2017-01-27 13:56 GMT+01:00 Jim Jagielski <j...@jagunet.com>:
>
> > On Jan 26, 2017, at 6:13 PM, Jacob Champion <champio...@gmail.com> wrote:
> >
> >
> > +1 (just not for 2.4.26, per my OP in the thread -- there is no way I can
> > find around the current PHP-FPM "fixups" without compatibility-breaking
> > behavior).
> >
>
> Let me relook over fpm-main... from what I saw, there are only 2
> logic paths: one if Apache and the other for everybody-else...
> and the Apache path only kicks in if it sees the proxy:balancer
> or proxy:fcgi prefix.
>
> My thought was to have mod_proxy_fcgi now start sending "correct"
> values for these envvars requiring NO fixups... ie, PHP-FPM
> will handle those envvars as it does for everybody else.
>
> Isn't that the better solution? Or is your concern about non PHP-FPM
> fcgi backends and *that* compatibility concern?
>
>
> HHVM is another important PHP FCGI backend that might be interesting to take
> into consideration. It seems that there is a check for mod_proxy_fcgi's
> prefix in here too:
>
> https://github.com/facebook/hhvm/blob/HHVM-3.17/hphp/runtime/server/fastcgi/fastcgi-transport.cpp#L243-L244
>
> Luca
