Hot answers tagged httpd
Looks like mod_security is working perfectly. It blocked the request because the Host header only contained an IP address, which is what this rule is meant to do. You should be using an actual hostname to refer to your web site, in production. It's also a good idea in development too, but if you need to use an IP address in development you can always ...
If you put both of these specifications into openssl ciphers -V and compare you will find that: 25 ciphers are contained in both sets. The set from Mozilla contains 6 SRP (secure remote password) ciphers which are not supported by the browsers. It also contains 7 ciphers using CAMELIA. I don't know which browser supports these ciphers but according to ...
The httpd resource does appear to be running (based on the pcs status output you've shown). Perhaps something stopped the service while Pacemaker was monitoring it, which would throw the error you see above, and trigger a recovery. If you grep your logs (on the DC: "Current DC: vda-zabserver-b - partition with quorum") for "LogActions", you should see any ...
I think the easiest solution is to move the directive from the server level to the virtualhost level, if the server-wide setting proves unacceptable for a vhost. Use a default Include in every vhost and omit it in the vhosts where you deviate from the norm. The new <If> (httpd 2.4) might be an option too.
$ sudo grep -ri lampp /etc should show you what did it. Maybe /etc/rc.local or some other cruddy init script.
Only top voted, non community-wiki answers of a minimum length are eligible