apache

fail2Ban is a very handy tool to prevent a lot of unwanted traffic from consuming bandwidth on your servers. It’s a minimal and relatively simple IDS Type Tool that comes with some predefined filters to automatically lockout potentially dangerous or bandwidth-consuming type attacks. 1. creating a custom filter /etc/fail2ban/filter.d/custom.conf [Definition] badagents = 360Spider|ZmEu|Auto Spider 1.0|zgrab/[0-9]*\.[0-9a-zA-Z]*|Wget\(.*\)|MauiBot.* failregex = ^.+?:\d+ <HOST> -.*"(GET|POST|HEAD).*HTTP.*(?:%(badagents)s)"$ ignoreregex = 2. test the custom filter against a log file using the following command fail2ban-regex /path-to-samples/sample....

Install modules Enable modules Method 1 using rewrite module RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L] </VirtualHost> Method 2 using redirect method Redirect permanent / https://www.yourdomain.com/ </VirtualHost>

Install and enable apache2 proxy modules proxies all requests (“/”) to a single backend: to point to the reverse proxy, instead of back to itself, the ProxyPassReverse directive is most often required: Only specific URIs can be proxied Example ServerName example.net Documentroot /var/www/html/ ProxyPass “/” “http://www.example.com/" ProxyPassReverse “/” “http://www.example.com/" </VirtualHost>

1. Configure DNS Records In order to set up the desired redirect, www.example.com to example.com or vice versa, you must have an A record for each name. 2. Enable the mod_rewrite module 3.1 Update site.conf or .htaccess file ( www to non-www) 3.2 Update site.conf or .htaccess file ( non-www to www) Example ServerName example.net Documentroot /var/www/html/ RewriteEngine on RewriteCond %{HTTP_HOST} ^www.yoursite.com RewriteRule (.*) http://yoursite.com/$1 [R=301,L] </VirtualHost>