Then you ARE using the current mod_proxy_fcgi and not the old one, it's
important to not confuse each when using / consulting docs, I suggest you
reading this:
https://wiki.apache.org/httpd/PHP-FPM
If you are truly using mod_proxy_fcgi then it's only PHP-FPM fault, not
httpd, you should not even
Hi Lewis,
This seems to be a problem inside mod_fcgi and not httpd, proxies in
general don't care about what's the language behind it, as long as the
protocol is being respected. Are you sure you are not getting into trouble
just because you are not using mod_proxy_fcgi instead?
Apache 2.4 docs
Simply to avoid assumptions, did you update php-fpm to 7 as well?
On Sun, Sep 30, 2018, 11:01 @lbutlr wrote:
> On 29 Sep 2018, at 21:02, Frank Gingras wrote:
> > As for the "filter_var" error, you're missing a php extension/module.
>
> No, I'm not. filter is built in to php and is properly
As for the "filter_var" error, you're missing a php extension/module.
On Sat, Sep 29, 2018 at 10:57 PM Frank Gingras wrote:
> "Primary Script Unknown" means that you're mapping to a non-existent
> resource on the fpm backend - remember that when using ProxyPassMatch, the
> request uri path is
"Primary Script Unknown" means that you're mapping to a non-existent
resource on the fpm backend - remember that when using ProxyPassMatch, the
request uri path is appended to the last path provided.
On Sat, Sep 29, 2018 at 5:06 PM @lbutlr wrote:
> On 29 Sep 2018, at 05:59, Frank Gingras
"Everything breaks" isn't really a useful statement. Be more specific if
you want more precise feedback.
On Sat, Sep 29, 2018 at 7:37 AM @lbutlr wrote:
> On 28 Sep 2018, at 16:15, Frank Gingras wrote:
> > Consider the wiki article:
> >
> > http://wiki.apache.org/httpd/php
>
> That's not
