Changes

Jump to navigation Jump to search

HT

74 bytes removed, 18:16, 29 November 2011
Updated link
This article will help you understand some aspects and build your knowledge advantages of the .htaccess file you see when you run an Apache Web Server like ours. '''''Note''': Article is still under editing''
==What is a .htaccess file?==
It is Apache's directory-level configuration file (as opposed to httpd.conf, which is the main server configuration file) that provides the governing rules of how a the web server should be ran/behaveoperates. When it is placed in a particular directory, the rules in it apply to that directory and all the subdirectories thereof.
Here is a [http://www.javascriptkit.com/howto/htaccess.shtml good tutorial] to on the use and configuration of the .htaccess file.
==What is a .htpasswd file?==
===Change the Default Directory Index File===
It can be used to chnage change the default index file , which is normally index.html, index.ext... to anything else, 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===
If you have ever wondered how people chnage change their 404, 500... error pages to something like lost.ext, then you will like this code in your .htaccess file:
<pre>
<nowiki>
</nowiki>
</pre>
Where [Error Number] is replaced with the error number, and [Error Document] is replaced with the path fo to the error document , which can be internal or external , as in:
<pre>http://www.anothersite.com/foo.ext or /foo.ext</pre>
===Limiting Access by User===
This part lets you use a .htaccess/.htpasswd user login system that which uses cookies. It is not fully safe only partly secure because the session does not expire until all open broswers browsers are closed , so try not to use it much on your a site section that needs foul fool-proof security. Here is the code:
<pre>
AuthType Basic
Require valid-user
</pre>
For this example , you places place 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_ServerThe_Uniform_Server|The 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/>
</Directory>
</pre>
If you are intrested in doing want to do this for just specific files , then use:
<pre>
<Files /path/to/file.ext>
</Files>
</pre>
The ''Require'' statement is used to list valid users or groups of users so if . If you just want 1 one .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:
Groupname2: username1 username4 username5 ....
</pre>
As you can see , a username may be in as many group groups as you like while others may just be in 1only one.
[[Category: Support]]
[[Category: Troubleshooting ]]
[[Category: Application]]
[[Category: Development]]

Navigation menu