We can do more with overrides than speed Apache up. This mechanism allows the webmaster to exert finer control over what is done in .htaccess files. The key directive is AllowOverride.
AllowOverride override1 override2 ... Directory
This directive tells Apache which directives in an .htaccess file can override earlier directives. The list of AllowOverride overrides is as follows:
Allows individual settings of AuthDBMGroupFile, AuthDBMUserFile, AuthGroupFile, AuthName, AuthType, AuthUserFile, and require
Allows AddType, AddEncoding, and AddLanguage
Allows FancyIndexing, AddIcon, AddDescription (see Chapter 7)
Can limit access based on hostname or IP number
Allows the use of the Options directive (see Chapter 4)
All of the above
None of the above
You might ask: if none switches multiple searches off, which of the above options switches it on? The answer is any of them, or the complete absence of AllowOverride. In other words, it is on by default.
To illustrate how this works, look at .../site.override, which is .../site.htaccess with the authentication directives on the salespeople's directory back in again. We have also, to make a visible difference, commented out:
require group cleaners
The Config file is as follows:
User webuser Group webgroup ServerName www.butterthlies.com AccessFilename .myaccess ServerAdmin email@example.com ...