Well... um... what do you suggest I change it to? (I have read the other guy's
suggestion and will be trying it as well.)
On 2015-03-23 at 4:45 PM, "Eric Covener" wrote:
>
>On Fri, Mar 20, 2015 at 10:01 PM,
>wrote:
>> RewriteCond %{REQUEST_FILENAME} -f
>
>
>in vhost context, REQUEST_FILENAME
On Fri, Mar 20, 2015 at 10:01 PM, wrote:
> RewriteCond %{REQUEST_FILENAME} -f
in vhost context, REQUEST_FILENAME is just the URL. It hasn't been
mapped to the filesystem yet.
--
Eric Covener
cove...@gmail.com
-
To unsubscrib
Although I am not sure why it is not defaulting to 404 either.
Kind Regards,
Scott
First Class Watches
9 Warwick Road
Kenilworth
CV8 1HD
Warwickshire
United Kingdom
On 23 March 2015 at 15:23, Scott (firstclasswatches.co.uk) <
scott.lu...@firstclasswatches.co.uk> wrote:
> Hello,
>
> Ok fair eno
Hello,
Ok fair enough. I don't think what I have is exotic, SetHandler is usually
how PHP is traditionally implemented in non FPM setups and this extends it
to mod_proxy_fcgi. If anybody spots any problems with my approach I would
love to hear about it but so far it has been stable.
For what you
Hey. I'm not saying that your method wouldn't work, but I feel very
uncomfortable deviating so far from the official guide. I don't want an exotic,
special configuration that is prone to break in the future. I really want to
know what's wrong with what I have, if anyone is able to tell. I really
Hello,
I believe that using a SetHandler approach (in my case with a UDS) is the
most reliable way to use mod_proxy_fcgi with PHP-FPM as I believe this
requires resolution of the script before it is passed to PHP-FPM.
ProxyErrorOverride On
Dear Apache HTTP Server community,
A few months ago, I finally switched over my PHP from using mod_php to PHP-FPM.
I have it mostly working, except for one very annoying thing that I hope you
can help me with.
For my test vhost, I have a config that has a lot of RewriteRules and ends with
this