Httpd Modules: Difference between revisions
| Line 21: | Line 21: | ||
==The List of Static Modules Compiled into the httpd Binary== | ==The List of Static Modules Compiled into the httpd Binary== | ||
{{Internal|httpd Static Module List|The List of Static Modules Compiled into the httpd Binary}} | |||
httpd | |||
=Modules= | =Modules= | ||
* [[httpd mod_proxy|mod_proxy]] | * [[httpd mod_proxy|mod_proxy]] | ||
* [[mod_cluster]] | * [[mod_cluster]] | ||
Revision as of 18:30, 5 January 2017
Internal
Overview
Static Modules vs Dynamic Modules
Support for a specific module can be statically linked into the httpd binary at compilation, by specifying it with a configuration option similar to "--enable-proxy", or the module can be loaded at runtime, if the Dynamic Shared Object (DSO) capability is enabled.
It is preferable to use shared modules which are loaded as needed with the LoadModule directive.
If a module is compiled with the intention to load it dynamically, the corresponding "enable" compilation flag should carry the "shared" value (example "--enable-proxy=shared"). Note that in order to be able to load modules dynamically, httpd must be compiled with the Dynamic Shared Object (DSO) capability enabled, which is turned by the --enable-so compilation flag.
Dynamic Shared Object (DSO) capability is enabled at compilation by using "--enable-so" option.