[users@httpd] Re: YOU BROKE MY CODE!

2014-05-17 Thread Christophe JAILLET
Le 17/05/2014 05:37, Andy Canfield a écrit : You broke my code! If something got broken, then something has changed. I imagine that you have upgraded your version of apache. Your are running 2.2.22. Which version of apache was used previously? CJ -

Re: [users@httpd] Trying to setup php-fpm with latest apache 2.4

2014-05-17 Thread David Herring
Thank you...yes On 16 May 2014 01:12, Jeff Trawick wrote: > You need mod_proxy_fcgi to interface with PHP-FPM. > > See http://wiki.apache.org/httpd/PHP-FPM > > (My previous attempts to post were rejected as suspected SPAM, so I'm > trying again without including the original message.) > > --

Re: [users@httpd] AH01144: No protocol handler was valid for the URL ...

2014-05-17 Thread David Herring
Thank you correct answer... yes how stupid I feel. Thanks again, Dave On 17 May 2014 06:49, Falco Schwarz wrote: > Hi Dave, > > you are trying to proxy to a fcgi backend so you need to enable the > proxy_fcgi_module. > > Falco > > On 17 May 2014, at 02:59, David Herring wrote: > > Excuse

Re: [users@httpd] YOU BROKE MY CODE!

2014-05-17 Thread Mackey, Harold A.
Same problem here. I have 4 worpress sites running on Apache2 using RHEL. Two weeks ago, I configured VirtualHosting according to documentation, and three of the four sites work flawlessly. One resolves with internal server errors. (The first one. This means something….) Here is how I got it t

Re: [users@httpd] YOU BROKE MY CODE!

2014-05-17 Thread Filipe Cifali
Use at your own risk. You probably haven't loaded mod authn on your config, check that. On Sat, May 17, 2014 at 12:37 AM, Andy Canfield wrote: > Last week, if you went to http://www.andycanfield.com, you would see my > web site. Today, if you go there, you will see "Internal Server Error". > A

[users@httpd] Re: mod_proxy and meta http-equiv=

2014-05-17 Thread C . E . Rau
Have a look at "ProxyHTMLMeta On". The directive enables mod_proxy_html to process the metas. (off by default) It's a little buggy in my testing though. The code that trips it up is esoteric enough that you may get lucky. (in my case - slightly malformed metas in comments were processed - par