HT: Difference between revisions
m
Reverted edits by Upazixorys (Talk); changed back to last version by Olajideolaolorun
Upazixorys (talk | contribs) No edit summary |
m (Reverted edits by Upazixorys (Talk); changed back to last version by Olajideolaolorun) |
||
| Line 1: | Line 1: | ||
This article will help you understand and build your knowledge of the .htaccess file you see when you run an Apache Web Server like ours. | This article will help you understand and build your knowledge of the .htaccess file you see when you run an Apache Web Server like ours. | ||
| Line 24: | Line 16: | ||
===Change the Default Directory Index File=== | ===Change the Default Directory Index File=== | ||
It can be used to chnage the default index file which is normally index.html, index.ext... to anything like foo.ext or whatever name/extension you prefer. To do this, use: | It can be used to chnage the default index file which is normally index.html, index.ext... to anything like foo.ext or whatever name/extension you prefer. To do this, use: | ||
<pre>DirectoryIndex foo.ext home.html home.php foo.php</pre> | |||
===Customizing Error Handling/Error Pages=== | ===Customizing Error Handling/Error Pages=== | ||
If you have ever wondered how people chnage their 404, 500... error pages to something like lost.ext, then you will like this code in your .htaccess file: | If you have ever wondered how people chnage their 404, 500... error pages to something like lost.ext, then you will like this code in your .htaccess file: | ||
<pre> | |||
<nowiki> | |||
ErrorDocument [Error Number] [Error Document] | ErrorDocument [Error Number] [Error Document] | ||
Error Document 404 /404.html | Error Document 404 /404.html | ||
</nowiki> | |||
</pre> | |||
Where [Error Number] is replaced with the error number, and [Error Document] is replaced with the path fo the error document which can be internal or external as in: | Where [Error Number] is replaced with the error number, and [Error Document] is replaced with the path fo the error document which can be internal or external as in: | ||
<pre>http://www.anothersite.com/foo.ext or /foo.ext</pre> | |||
===Server Generated URL Redirects=== | ===Server Generated URL Redirects=== | ||
You moved or renamed a directory and you know people still have the old directory bookmarked so you want them to be redirected to the new directory, then you can use this code: | You moved or renamed a directory and you know people still have the old directory bookmarked so you want them to be redirected to the new directory, then you can use this code: | ||
<pre>Redirect [Trigger] [New Destination] | |||
Redirect /old http://www.url.com/new | Redirect /old http://www.url.com/new | ||
Redirect /old /new | Redirect /old /new</pre> | ||
===Limiting Access by Hostname/IP Address=== | ===Limiting Access by Hostname/IP Address=== | ||
Use this section of this article if you are intrested in blocking access to a file/folder on your server: | Use this section of this article if you are intrested in blocking access to a file/folder on your server: | ||
<pre> | |||
<Files admin.cgi> | |||
order deny, allow | order deny, allow | ||
deny from ALL | deny from ALL | ||
allow from 1.2.3.4 | allow from 1.2.3.4 | ||
</Files> | |||
</pre> This example denies access to admin.cgi to everyone but the owner of the IP Address mention in ''1.2.3.4''. You can also use this for a folder, in that case you would replace admin.cgi with the name of the folder. If you are intrested in using the Hostname rather than the IP then use: | |||
<pre> | |||
<Files admin.cgi> | |||
order deny, allow | order deny, allow | ||
deny from ALL | deny from ALL | ||
allow from mymachine.networkdomain.com | allow from mymachine.networkdomain.com | ||
</Files> | |||
</pre> | |||
You can also use it for your whole network to have access to it alone, example: | You can also use it for your whole network to have access to it alone, example: | ||
<pre> | |||
# IP Number | # IP Number | ||
<Files admin.cgi> | |||
order deny, allow | order deny, allow | ||
deny from ALL | deny from ALL | ||
allow from 192.168.123 | allow from 192.168.123 | ||
</Files> | |||
# Hostname | # Hostname | ||
<Files admin.cgi> | |||
order deny, allow | order deny, allow | ||
deny from ALL | deny from ALL | ||
allow from .networkdomain.com | allow from .networkdomain.com | ||
</Files> | |||
</pre> | |||
Where ''192.168.123'' is your internal network IP and .networkdomain.com is your Hostname/Domain. You can also switch it to allow from ALL and deny from a list of IPs or Hostnames.Here is a pratical example for advance users: | Where ''192.168.123'' is your internal network IP and .networkdomain.com is your Hostname/Domain. You can also switch it to allow from ALL and deny from a list of IPs or Hostnames.Here is a pratical example for advance users: | ||
<pre> | |||
<Files [/path/filename]> | |||
[Attributes to apply to file...] | [Attributes to apply to file...] | ||
</files> | |||
</pre> | |||
===Limiting Access by User=== | ===Limiting Access by User=== | ||
This part lets you use a .htaccess/.htpasswd user login system that uses cookies. It is not fully safe because the session does not expire until all open broswers are closed so try not to use it much on your site section that needs foul proof security. Here is the code: | This part lets you use a .htaccess/.htpasswd user login system that uses cookies. It is not fully safe because the session does not expire until all open broswers are closed so try not to use it much on your site section that needs foul proof security. Here is the code: | ||
<pre> | |||
AuthType Basic | AuthType Basic | ||
AuthName | AuthName "Restricted Access" | ||
AuthUserFile /htpasswd/path/to/.htpasswd | AuthUserFile /htpasswd/path/to/.htpasswd | ||
Require valid-user | Require valid-user | ||
</pre> | |||
For this example you places a .htpasswd file in the path (/htpasswd/path/to/). In the .htpasswd file will be: | For this example you places a .htpasswd file in the path (/htpasswd/path/to/). In the .htpasswd file will be: <pre>[user]:[password]</pre> Normally you have to encrypt the password but if you are using The [[Uniform_Server|Uniform Server]], then you do not need to do that. You ca also use this example to protect another directory from just 1 .htaccess file: | ||
<pre> | |||
<Directory /path/to/> | |||
AuthType Basic | AuthType Basic | ||
AuthName | AuthName "Restricted Access" | ||
AuthUserFile /htpasswd/path/to/.htpasswd | AuthUserFile /htpasswd/path/to/.htpasswd | ||
Require valid-user | Require valid-user | ||
</Directory> | |||
</pre> | |||
If you are intrested in doing this for just specific files then use: | If you are intrested in doing this for just specific files then use: | ||
<pre> | |||
<Files /path/to/file.ext> | |||
AuthType Basic | AuthType Basic | ||
AuthName | AuthName "Restricted Access" | ||
AuthUserFile /htpasswd/path/to/.htpasswd | AuthUserFile /htpasswd/path/to/.htpasswd | ||
Require valid-user | Require valid-user | ||
</Files> | |||
</pre> | |||
The ''Require'' statement is used to list valid users or groups of users so if you just want 1 .htpasswd file, but want multiple protected areas, then you can use: | The ''Require'' statement is used to list valid users or groups of users so if you just want 1 .htpasswd file, but want multiple protected areas, then you can use: | ||
<pre>Require user username1 username2 username3...</pre> | |||
Or if you want to use it in groups then you can use: | Or if you want to use it in groups then you can use: | ||
<pre> | |||
AuthGroupFile /htgorups/path/to/.htgroups | AuthGroupFile /htgorups/path/to/.htgroups | ||
Require group groupname1 groupname2 groupname3... | Require group groupname1 groupname2 groupname3... | ||
</pre> | |||
And in the ''.htgroups'' file would be: | And in the ''.htgroups'' file would be: | ||
<pre> | |||
Groupname1: username1 username2 username3 ... | Groupname1: username1 username2 username3 ... | ||
Groupname2: username1 username4 username5 .... | Groupname2: username1 username4 username5 .... | ||
</pre> | |||
As you can see a username may be in as many group as you like while others may just be in 1. | As you can see a username may be in as many group as you like while others may just be in 1. | ||