Tag Info

Hot answers tagged

4

I often find such divergent behaviour can be attributed to differences in configuration. For that, I wrote a script (httpd-dump-config) to flatten httpd.conf so I could diff it so I could audit for such differences between cluster nodes or between environments (even over SSH) It won't check .htaccess files though, but it can still help to find easily ...


3

I'd do it via iptables. Pingdom have a specific set of IP addresses they use, and, unsurprisingly, make the list public. https://support.pingdom.com/Knowledgebase/Article/View/16/0/where-can-i-find-a-list-of-ip-addresses-for-the-pingdom-probe-servers You could retrieve the list, and script the process of creating iptables drop rules for them.


1

This should work : RewriteCond %{QUERY_STRING} &searchstring=([^&]+) [NC] RewriteRule ^index\.php$ /search/node/%1? [R=301,L] Basically, first search for the searchstring parameter in query string. The searching parameter value is put in a variable called %1 Then replace index.php with /search/node/%1 E.g : From this : ...


1

Unless an .htaccess file has been created before, you'll just need to create one in a relevant directory - for example, if you want a redirect from /foo/bar.html you can put the .htaccess file in the web root (/) or in the /foo directory. From there, you'll just want to use mod_alias for a simple redirect: Redirect /foo/bar.html ...


1

Try the block below, I just tested it myself on one of my Apache setups and it worked fine. <IfModule mod_rewrite.c> RewriteEngine on SetEnvIfNoCase User-Agent ^libwww-perl bad_bot Order Allow,Deny Allow from ALL Deny from env=bad_bot



Only top voted, non community-wiki answers of a minimum length are eligible