apache tutorial - .htaccess - apache - apache web server - apache server - apache2

.htaccess features 7 : Redirect to Maintenance Page + allowing particular IP

• Redirecting visitors to a maintenance page or other temporary page is an essential tool to have in your tool belt. Using HTAccess, redirecting visitors to a temporary maintenance page is simple and effective.
• All you need to redirect your visitors is the following code placed in your site’s root HTAccess:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{REMOTE_ADDR} !^123\.456\.789\.000
RewriteCond %{REQUEST_URI} !/maintenance.html$ [NC]
RewriteCond %{REQUEST_URI} !\.(jpe?g?|png|gif) [NC]
RewriteRule .* /maintenance.html [R=302,L]
</IfModule>

.htaccess features 8 : Redirect www to non-www

rewriterule htaccess :

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www. wikitechy.com [NC]
RewriteRule ^(.*)$ http://wikitechy.com/$1 [L,R=301]

.htaccess features 9 : Redirect non-www to www

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^ wikitechy.com [NC]
RewriteRule ^(.*)$ http://www. wikitechy.com/$1 [L,R=301]

• Just replace wikitechy.com with your website and you can put this code in .htaccess file in your apache web server,
• Both of these rules send a full search engine friendly 301 HTTP redirect. They also preserve the entire URL (so yoursite.com/about redirects to www.yoursite.com/about).

.htaccess features 10 : Visitor IP Banning

<Limit GET POST>
order allow,deny
deny from 42.12.5.34
deny from 193.110.145.185
deny from 212.173.53.
deny from 69.242.
allow from all
</Limit>

.htaccess features 11 : Disable Hot Linking

rewriterule htaccess :

RewriteEngine on
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www\.)?wikitechy.com/.*$ [NC]
RewriteCond %{HTTP_REFERER} !^http://(www\.)? cheap-hosting.wikitechy.com.com/.*$ [NC]
RewriteRule \.(gif|jpg|jpeg|png|js|css)$ - [F]

.htaccess features 12 : Prevent viewing of .htaccess file

• If you use htaccess for password protection, then the location containing all of your password information is plainly available through the htaccess file.
• If you have set incorrect permissions or if your server is not as secure as it could be, a browser has the potential to view an htaccess file through a standard web interface and thus compromise your site/server.
• However, it is possible to prevent an htaccess file from being viewed in this manner:

<Files .htaccess>
order allow,deny
deny from all
</Files>

.htaccess features 13 : htaccess password - Protecting Files or Directories with .htaccess and .htpasswd

• .htaccess and .htpasswd files - These two files work hand-in-hand to require a valid username and password when accessing a file; if no such password is provided, they simply display a “Restricted Access” error message and the invalid user is turned away.
• This is the perfect way to protect
• sensitive files,
• administration areas,
• sensitive login screens, from malicious hackers
• htaccess htpasswd - The first step in this process is to create an .htpasswd file and place it into the directory where the protected file is located.
• If it’s protecting a given directory, the .htpasswd file should be placed inside that protected directory.
• The content of the file is really easy to create, as it contains a username and password separated by a colon. Here’s the basic setup:

• That single line of text goes into the .htpasswd file and that file is immediately uploaded to the server. If there should be more than one user and password combination that can grant access to the file or directory, they can be listed on separate lines with the .htpasswd document.
• To create the authentication screen that requires one of the valid username and password combinations to be entered, site administrators need to add the following series of lines to their.htaccess file, requiring the password document and assigning it to a given directory or file:

AuthUserFile /server/path/of/.htpasswd
AuthType Basic
AuthName "The Title of the Protected Page Goes Here"
<Files "login.php">
Require ValidUser
</Files>

• All you needs to do is to point to the relevant .htpasswd file, specify the file or director being protected, and then give the page a title. That title will appear within the login form that is automatically generated by the browser when it encounters this restriction.