Apache Core Features
These configuration parameters control the core Apache features, and are always available.
Directives
AccessConfig
AccessFileName
AddModule
AllowOverride
AuthName
AuthType
BindAddress
BS2000Account
ClearModuleList
ContentDigest
CoreDumpDirectory
DefaultType
<Directory>
<DirectoryMatch>
DocumentRoot
ErrorDocument
ErrorLog
<Files>
<FilesMatch>
Group
HostNameLookups
IdentityCheck
<IfDefine>
<IfModule>
Include
KeepAlive
KeepAliveTimeout
<Limit>
<LimitExcept>
LimitRequestBody
LimitRequestFields
LimitRequestFieldsize
LimitRequestLine
Listen
ListenBacklog
<Location>
<LocationMatch>
LockFile
LogLevel
MaxClients
MaxKeepAliveRequests
MaxRequestsPerChild
MaxSpareServers
MinSpareServers
NameVirtualHost
Options
PidFile
Port
require
ResourceConfig
RLimitCPU
RLimitMEM
RLimitNPROC
Satisfy
ScoreBoardFile
ScriptInterpreterSource
SendBufferSize
ServerAdmin
ServerAlias
ServerName
ServerPath
ServerRoot
ServerSignature
ServerTokens
ServerType
StartServers
ThreadsPerChild
TimeOut
UseCanonicalName
User
<VirtualHost>
AccessConfig directive
Syntax: AccessConfig filename
Default: AccessConfig conf/access.conf
Context: server config, virtual host
Status: core
The server will read this file for more directives after reading the ResourceConfig file. Filename is relative to the ServerRoot. This feature can be disabled using:
AccessConfig /dev/null
Historically, this file only contained <Directory> sections; in fact it can now contain any server directive allowed in the server config context.
AccessFileName directive
Syntax: AccessFileName filename filename ...
Default: AccessFileName .htaccess
Context: server config, virtual host
Status: core
Compatibility: AccessFileName can accept more than one filename only in Apache 1.3 and later
When returning a document to the client the server looks for the first existing access control file from this list of names in every directory of the path to the document, if access control files are enabled for that directory. For example:
AccessFileName .acl
before returning the document /usr/local/web/index.html, the server will read /.acl, /usr/.acl, /usr/local/.acl and /usr/local/web/.acl for directives, unless they have been disabled with
<Directory />
AllowOverride None
</Directory>
AddModule directive
Syntax: AddModule module module ...
Context: server config
Status: core
Compatibility: AddModule is only available in Apache 1.2 and later
The server can have modules compiled in which are not actively in use. This directive can be used to enable the use of those modules. The server comes with a pre-loaded list of active modules; this list can be cleared with the ClearModuleList directive.
AllowOverride directive
Syntax: AllowOverride override override ...
Default: AllowOverride All
Context: directory
Status: core
When the server finds an .htaccess file (as specified by AccessFileName) it needs to know which directives declared in that file can override earlier access information.
Override can be set to None, in which case the server will not read the file, All in which case the server will allow all the directives, or one or more of the following:
AuthConfig: Allow use of the authorization directives ( AuthDBMGroupFile, AuthDBMUserFile, AuthGroupFile, AuthName, AuthType, AuthUserFile, require, etc.).
FileInfo: Allow use of the directives controlling document types ( AddEncoding, AddLanguage, AddType, DefaultType, ErrorDocument, LanguagePriority, etc.).
Indexes: Allow use of the directives controlling directory indexing ( AddDescription, AddIcon, AddIconByEncoding, AddIconByType, DefaultIcon, DirectoryIndex, FancyIndexing, HeaderName, IndexIgnore, IndexOptions, ReadmeName, etc.).
Limit: Allow use of the directives controlling host access (allow, deny and order).
Options: Allow use of the directives controlling specific directory features ( Options and XBitHack).
» |
