Working with Dynamic Access Control FilesChapter 8 Controlling Access to Your Server 195PathCheck fn="htaccess-find".htaccess processing should be the last PathCheck directive in the object.b. To activate .htaccess file processing for particular server directories,place the PathCheck directive in the corresponding definition inmagnus.conf.7. To name your .htaccess files something other than .htaccess, you mustspecify the filename in the PathCheck directive using the following format:PathCheck fn="htaccess-find" filename="filename"Subsequent access to the server will be subject to .htaccess access control in thespecified directories. For example, to restrict write access to .htaccess files, createa configuration style for them, and apply access control to that configuration style.For more information, see Chapter 17, “Applying Configuration Styles.”Converting Existing .nsconfig Files to .htaccess FilesEnterprise Server 6.0 includes the htconvert plug-in for converting your existing.nsconfig files to .htaccess files. The .nsconfig files are no longer supported. Ifyou have been using.nsconfig files, you should convert them to .htaccess files.When activated, htconvert searches the given server.xml files for pfx2dir anddocument-root directives. Each .nsconfig file found will be translated into an.htaccess file. Multiple obj.conf files can be converted depending onconfiguration.The htconvert plug-in currently only supports the RestrictAccess andRequireAuth directives, and the wrapper. If other than are presented, the script will give a warning and behave as though allfiles in the directory are to be access-controlled.NOTE The next time you use the Administration Server, you will bewarned that manual edits have been applied. Click Apply to acceptyour changes.NOTE If there is an existing .htaccess file, htconvert will produce an.htaccess.new file, and give a warning. If .htaccess and.htaccess.new already exist, the new file will be named.htaccess.new.new. The.new will be repeatedly appended.
