InterSET

.htaccess to restrict access to Files and Directories

.htaccess to restrict access to Files and Directories

Share Now:

Share on facebook
Share on linkedin
Share on twitter
Share on email

Apache server allows access to everything inside the Document Root folder by default.

This means all the subdirectories and their contents can be listed and accessed from the web. However, you can use .htaccess to harden the security of your Apache Server. The .htaccess is a configuration file, which if detected will be executed by Apache.

If you already have a .htaccess file in your Document Root Folder, back it up before making any changes. Edit or create a new .htaccess file.

The three most important security settings you should consider adding to your .htaccess file are:

1. Deny Access to .htaccess Itself

Add the following lines in your .htaccess file to prevent access to the .htaccess file itself.

# Deny access to .htaccess
<Files .htaccess>
Order allow,deny
Deny from all
</Files>

2. Disable Directory Indexing

The following line in .htaccess will remove directory indexing and make the server respond with a 403 forbidden message.

# Disable directory browsing 
Options -Indexes

To simply hide all the contents of the directory without a forbidden message, use the IndexIgnore directive.

# Hide the contents of directories
IndexIgnore *

To hide some filetypes only, use

# Hide files of type .png, .zip, .jpg, .gif and .doc from listing
IndexIgnore *.png *.zip *.jpg *.gif *.doc

3. Prevent access to certain files

Even if you remove directories and files from the listing, they are still accessible if you type the path.

To remove unauthorized access to certain file extensions, use

# Deny access to files with extensions .ini, .psd, .log, .sh
<FilesMatch "\.(ini|psd|log|sh)$">
Order allow,deny
Deny from all
</FilesMatch>

To prevent access to all filenames starting with dot(.) like .htaccess, .htpasswd, .env and others use

# Deny access to filenames starting with dot(.)
<FilesMatch "^\.">
Order allow,deny
Deny from all
</FilesMatch>

You may also password-protect files and directories and store the passwords in a .htpasswd file

# Password protect files
<FilesMatch "^(execute|index|myfile|anotherfile)*$">
AuthType Basic
AuthName "Mypassword"
AuthUserFile <Full Server Path to .htpasswd file>/.htpasswd
Require valid-user
</FilesMatch>

Replace the <Full Server Path to .htpasswd file> with your actual path.

You may also place a .htaccess file inside each sub-directory with specific overrides. The access rules can be directly defined inside Apache’s main configuration file httpd.conf. But if you don’t have access to the main configuration file (which is normally the case if you are using a shared hosting service), you have to resort to .htaccess based access rules.

Note: Over-riding httpd.conf settings using .htaccess is only allowed if the AllowOverride Directive is set inside httpd.conf which is the default case.

0 0 votes
Reviewer Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments

Get Free Access to InterSet’s 1 GB SSD Hosting with Website Design


Know Your Entity Destiny Offers Savings

More You Would be interested in . . .

Have you any Question ?
Ask us !

0
Would love your thoughts, please comment.x
()
x