[1]Modules | [2]Directives | [3]FAQ | [4]Glossary | [5]Sitemap

   Apache HTTP Server Version 2.4

   [6] [8]HTTP Server > [9]Documentation > [10]Version 2.4

Configuration Files

   Available Languages: [11] de  | [12] en  | [13] fr  | [14] ja  | [15] ko  |
   [16] tr

   This document describes the files used to configure Apache HTTP Server.
   [17]Support Apache!
     * [18]Main Configuration Files
     * [19]Syntax of the Configuration Files
     * [20]Modules
     * [21]Scope of Directives
     * [22].htaccess Files

See also

     * [23]Comments

   [24]top

Main Configuration Files

   Related Modules Related Directives
     * [25]mod_mime

     * [26]
     * [27]Include
     * [28]TypesConfig

   Apache HTTP Server is configured by placing [29]directives in plain text
   configuration files. The main configuration file is usually called httpd.conf.
   The location of this file is set at compile-time, but may be overridden with the
   -f command line flag. In addition, other configuration files may be added using
   the [30]Include directive, and wildcards can be used to include many
   configuration files. Any directive may be placed in any of these configuration
   files. Changes to the main configuration files are only recognized by httpd when
   it is started or restarted.

   The server also reads a file containing mime document types; the filename is set
   by the [31]TypesConfig directive, and is mime.types by default.
   [32]top

Syntax of the Configuration Files

   httpd configuration files contain one directive per line. The backslash "\" may
   be used as the last character on a line to indicate that the directive continues
   onto the next line. There must be no other characters or white space between the
   backslash and the end of the line.

   Arguments to directives are separated by whitespace. If an argument contains
   spaces, you must enclose that argument in quotes.

   Directives in the configuration files are case-insensitive, but arguments to
   directives are often case sensitive. Lines that begin with the hash character "#"
   are considered comments, and are ignored. Comments may not be included on the
   same line as a configuration directive. White space occurring before a directive
   is ignored, so you may indent directives for clarity. Blank lines are also
   ignored.

   The values of variables defined with the [33]Define of or shell environment
   variables can be used in configuration file lines using the syntax ${VAR}. If
   "VAR" is the name of a valid variable, the value of that variable is substituted
   into that spot in the configuration file line, and processing continues as if
   that text were found directly in the configuration file. Variables defined with
   [34]Define take precedence over shell environment variables. If the "VAR"
   variable is not found, the characters ${VAR} are left unchanged, and a warning is
   logged. Variable names may not contain colon ":" characters, to avoid clashes
   with [35]RewriteMap's syntax.

   Only shell environment variables defined before the server is started can be used
   in expansions. Environment variables defined in the configuration file itself,
   for example with [36]SetEnv, take effect too late to be used for expansions in
   the configuration file.

   The maximum length of a line in normal configuration files, after variable
   substitution and joining any continued lines, is approximately 16 MiB. In
   [37].htaccess files, the maximum length is 8190 characters.

   You can check your configuration files for syntax errors without starting the
   server by using apachectl configtest or the -t command line option.

   You can use [38]mod_info's -DDUMP_CONFIG to dump the configuration with all
   included files and environment variables resolved and all comments and
   non-matching [39] and [40] sections removed. However, the
   output does not reflect the merging or overriding that may happen for repeated
   directives.
   [41]top

Modules

   Related Modules Related Directives
     * [42]mod_so

     * [43]
     * [44]LoadModule

   httpd is a modular server. This implies that only the most basic functionality is
   included in the core server. Extended features are available through [45]modules
   which can be loaded into httpd. By default, a [46]base set of modules is included
   in the server at compile-time. If the server is compiled to use [47]dynamically
   loaded modules, then modules can be compiled separately and added at any time
   using the [48]LoadModule directive. Otherwise, httpd must be recompiled to add or
   remove modules. Configuration directives may be included conditional on a
   presence of a particular module by enclosing them in an [49] block.
   However,  blocks are not required, and in some cases may mask the fact
   that you're missing an important module.

   To see which modules are currently compiled into the server, you can use the -l
   command line option. You can also see what modules are loaded dynamically using
   the -M command line option.
   [50]top

Scope of Directives

   Related Modules Related Directives
     * [51]
     * [52]
     * [53]
     * [54]
     * [55]
     * [56]
     * [57]

   Directives placed in the main configuration files apply to the entire server. If
   you wish to change the configuration for only a part of the server, you can scope
   your directives by placing them in [58], [59],
   [60], [61], [62], and [63] sections.
   These sections limit the application of the directives which they enclose to
   particular filesystem locations or URLs. They can also be nested, allowing for
   very fine grained configuration.

   httpd has the capability to serve many different websites simultaneously. This is
   called [64]Virtual Hosting. Directives can also be scoped by placing them inside
   [65] sections, so that they will only apply to requests for a
   particular website.

   Although most directives can be placed in any of these sections, some directives
   do not make sense in some contexts. For example, directives controlling process
   creation can only be placed in the main server context. To find which directives
   can be placed in which sections, check the [66]Context of the directive. For
   further information, we provide details on [67]How Directory, Location and Files
   sections work.
   [68]top

.htaccess Files

   Related Modules   Related Directives
     * [69]AccessFileName
     * [70]AllowOverride

   httpd allows for decentralized management of configuration via special files
   placed inside the web tree. The special files are usually called .htaccess, but
   any name can be specified in the [71]AccessFileName directive. Directives placed
   in .htaccess files apply to the directory where you place the file, and all
   sub-directories. The .htaccess files follow the same syntax as the main
   configuration files. Since .htaccess files are read on every request, changes
   made in these files take immediate effect.

   To find which directives can be placed in .htaccess files, check the [72]Context
   of the directive. The server administrator further controls what directives may
   be placed in .htaccess files by configuring the [73]AllowOverride directive in
   the main configuration files.

   For more information on .htaccess files, see the [74].htaccess tutorial.

   Available Languages: [75] de  | [76] en  | [77] fr  | [78] ja  | [79] ko  |
   [80] tr

   [81]top

Comments

   Notice:
   This is not a Q&A section. Comments placed here should be pointed towards
   suggestions on improving the documentation or server, and may be removed by our
   moderators if they are either implemented or considered invalid/off-topic.
   Questions on how to manage the Apache HTTP Server should be directed at either
   our IRC channel, #httpd, on Libera.chat, or sent to our [82]mailing lists.

   Copyright 2024 The Apache Software Foundation.
   Licensed under the [83]Apache License, Version 2.0.

   [84]Modules | [85]Directives | [86]FAQ | [87]Glossary | [88]Sitemap

References

   1. https://httpd.apache.org/docs/current/mod/
   2. https://httpd.apache.org/docs/current/mod/directives.html
   3. http://wiki.apache.org/httpd/FAQ
   4. https://httpd.apache.org/docs/current/glossary.html
   5. https://httpd.apache.org/docs/current/sitemap.html
   6. https://httpd.apache.org/docs/current/
   7. http://www.apache.org/
   8. http://httpd.apache.org/
   9. http://httpd.apache.org/docs/
  10. https://httpd.apache.org/docs/current/
  11. https://httpd.apache.org/docs/current/de/configuring.html
  12. https://httpd.apache.org/docs/current/en/configuring.html
  13. https://httpd.apache.org/docs/current/fr/configuring.html
  14. https://httpd.apache.org/docs/current/ja/configuring.html
  15. https://httpd.apache.org/docs/current/ko/configuring.html
  16. https://httpd.apache.org/docs/current/tr/configuring.html
  17. https://www.apache.org/foundation/contributing.html
  18. https://httpd.apache.org/docs/current/configuring.html#main
  19. https://httpd.apache.org/docs/current/configuring.html#syntax
  20. https://httpd.apache.org/docs/current/configuring.html#modules
  21. https://httpd.apache.org/docs/current/configuring.html#scope
  22. https://httpd.apache.org/docs/current/configuring.html#htaccess
  23. https://httpd.apache.org/docs/current/configuring.html#comments_section
  24. https://httpd.apache.org/docs/current/configuring.html#page-header
  25. https://httpd.apache.org/docs/current/mod/mod_mime.html
  26. https://httpd.apache.org/docs/current/mod/core.html#ifdefine
  27. https://httpd.apache.org/docs/current/mod/core.html#include
  28. https://httpd.apache.org/docs/current/mod/mod_mime.html#typesconfig
  29. https://httpd.apache.org/docs/current/mod/directives.html
  30. https://httpd.apache.org/docs/current/mod/core.html#include
  31. https://httpd.apache.org/docs/current/mod/mod_mime.html#typesconfig
  32. https://httpd.apache.org/docs/current/configuring.html#page-header
  33. https://httpd.apache.org/docs/current/mod/core.html#define
  34. https://httpd.apache.org/docs/current/mod/core.html#define
  35. https://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewritemap
  36. https://httpd.apache.org/docs/current/mod/mod_env.html#setenv
  37. https://httpd.apache.org/docs/current/configuring.html#htaccess
  38. https://httpd.apache.org/docs/current/mod/mod_info.html
  39. https://httpd.apache.org/docs/current/mod/core.html#ifdefine
  40. https://httpd.apache.org/docs/current/mod/core.html#ifmodule
  41. https://httpd.apache.org/docs/current/configuring.html#page-header
  42. https://httpd.apache.org/docs/current/mod/mod_so.html
  43. https://httpd.apache.org/docs/current/mod/core.html#ifmodule
  44. https://httpd.apache.org/docs/current/mod/mod_so.html#loadmodule
  45. https://httpd.apache.org/docs/current/mod/
  46. https://httpd.apache.org/docs/current/mod/module-dict.html#Status
  47. https://httpd.apache.org/docs/current/dso.html
  48. https://httpd.apache.org/docs/current/mod/mod_so.html#loadmodule
  49. https://httpd.apache.org/docs/current/mod/core.html#ifmodule
  50. https://httpd.apache.org/docs/current/configuring.html#page-header
  51. https://httpd.apache.org/docs/current/mod/core.html#directory
  52. https://httpd.apache.org/docs/current/mod/core.html#directorymatch
  53. https://httpd.apache.org/docs/current/mod/core.html#files
  54. https://httpd.apache.org/docs/current/mod/core.html#filesmatch
  55. https://httpd.apache.org/docs/current/mod/core.html#location
  56. https://httpd.apache.org/docs/current/mod/core.html#locationmatch
  57. https://httpd.apache.org/docs/current/mod/core.html#virtualhost
  58. https://httpd.apache.org/docs/current/mod/core.html#directory
  59. https://httpd.apache.org/docs/current/mod/core.html#directorymatch
  60. https://httpd.apache.org/docs/current/mod/core.html#files
  61. https://httpd.apache.org/docs/current/mod/core.html#filesmatch
  62. https://httpd.apache.org/docs/current/mod/core.html#location
  63. https://httpd.apache.org/docs/current/mod/core.html#locationmatch
  64. https://httpd.apache.org/docs/current/vhosts/
  65. https://httpd.apache.org/docs/current/mod/core.html#virtualhost
  66. https://httpd.apache.org/docs/current/mod/directive-dict.html#Context
  67. https://httpd.apache.org/docs/current/sections.html
  68. https://httpd.apache.org/docs/current/configuring.html#page-header
  69. https://httpd.apache.org/docs/current/mod/core.html#accessfilename
  70. https://httpd.apache.org/docs/current/mod/core.html#allowoverride
  71. https://httpd.apache.org/docs/current/mod/core.html#accessfilename
  72. https://httpd.apache.org/docs/current/mod/directive-dict.html#Context
  73. https://httpd.apache.org/docs/current/mod/core.html#allowoverride
  74. https://httpd.apache.org/docs/current/howto/htaccess.html
  75. https://httpd.apache.org/docs/current/de/configuring.html
  76. https://httpd.apache.org/docs/current/en/configuring.html
  77. https://httpd.apache.org/docs/current/fr/configuring.html
  78. https://httpd.apache.org/docs/current/ja/configuring.html
  79. https://httpd.apache.org/docs/current/ko/configuring.html
  80. https://httpd.apache.org/docs/current/tr/configuring.html
  81. https://httpd.apache.org/docs/current/configuring.html#page-header
  82. https://httpd.apache.org/lists.html
  83. http://www.apache.org/licenses/LICENSE-2.0
  84. https://httpd.apache.org/docs/current/mod/
  85. https://httpd.apache.org/docs/current/mod/directives.html
  86. http://wiki.apache.org/httpd/FAQ
  87. https://httpd.apache.org/docs/current/glossary.html
  88. https://httpd.apache.org/docs/current/sitemap.html