Enabling .Htaccess From The User Interface - Netscape ENTREPRISE SERVER 6.1 - 04-2002 ADMINISTRATOR Administrator's Manual

Working with Dynamic Access Control Files
You can use
control. The standard access controls are always applied before any
access control, regardless of the ordering of
user authentication with both standard and
user-group authentication is 'Basic' You could use SSL client authentication via the
standard server access control, and also require HTTP 'Basic' authentication via an
.htaccess
This section includes the following topics:
•

Enabling .htaccess from the User Interface

• Enabling .htaccess from magnus.conf
• Converting Existing .nsconfig Files to .htaccess Files
• Using htaccess-register
• Example of an .htaccess File
Enabling .htaccess from the User Interface
To configure your Enterprise Server to use
steps:
Access the Server Manager and select the server instance you wish to enable
1.
.htaccess
Click on the Class Manager link at the top of the screen.
2.
Select the Content Mgmt tab.
3.
Click on the
4.
Select the server to edit by:
5.
Select Yes to activate
6.
Enter the file name where you want the .
7.
Click OK.
8.
When finished, click Apply.
9.
Select hard start /restart or dynamically apply.
10.
196 Netscape Enterprise Server Administrator's Guide • April 2002 (Draft)
files in combination with the server's standard access
.htaccess
file.
for.
Configuration link.
.htaccess
Choosing the entire server or a specific server from the drop-down list
Choosing the directory and files to edit by clicking Browse
Choosing a wildcard pattern to edit by clicking Wildcard
.htaccess
directives. Do not require
PathCheck
access control when
.htaccess
, perform the following
.htaccess
.
configuration to be added.
htaccess
.htaccess