138
edits
Htaccess: Difference between revisions
→.htaccess file
mNo edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 34: | Line 34: | ||
With the password file and protected directory in place all that remains is the .htaccess file to tie it all together. The .htaccess file is what will tell the Webserver that the directory is password protected and requires authorisation. | With the password file and protected directory in place all that remains is the .htaccess file to tie it all together. The .htaccess file is what will tell the Webserver that the directory is password protected and requires authorisation. | ||
Change to your protected directory by typing: | Change to your protected directory by typing: | ||
| Line 44: | Line 42: | ||
Copy and paste the contents of the sample htaccess file into the editor, making the necessary modification to the AuthUserFile line, e.g. | Copy and paste the contents of the sample htaccess file into the editor, making the necessary modification to the AuthUserFile line, e.g. | ||
AuthType Basic | |||
AuthName "User Login" | |||
AuthUserFile /home/member/g/gizmo/passwd | AuthUserFile /home/member/g/gizmo/passwd | ||
require valid-user | |||
'''Note:''' keep the name of the file .htaccess - this is an actual file extension recognised by Apache and it must be used. | '''Note:''' keep the name of the file .htaccess - this is an actual file extension recognised by Apache and it must be used. | ||
| Line 51: | Line 51: | ||
Lastly we need to set the permission on the file by typing: | Lastly we need to set the permission on the file by typing: | ||
chmod | chmod 644 .htaccess | ||
== htaccess & pubcookie == | |||
You can use your htaccess file with the RedBrick pubcookie system. With this you can restrict access to redbrick members. See [[PubCookie on Redbrick]] for more. | |||
== Testing == | == Testing == | ||