ApacheConfigFilter
The ApacheConfigFilter is used for the integration of optional Apache modules and directives, see also the chapter Optional Apache modules. The filter copies the configuration as is, into the generated httpd configuration file. The ApacheConfigFilter makes it possible to configure any httpd directive, including mod_ssl directives.
To avoid confusion, we recommend configuring one ApacheConfigFilter that defines the server configuration and the host configuration. As long as this ApacheConfigFilter only configures the ServerConfig or HostConfig parameters, there is no need to map the filter to a URI. Additionally, configure one or more ApacheConfigFilter that define the location configuration, by setting the filter parameter LocationConfig. Map these filters to the location where the configuration should be added.
ch::nevis::navajo::apglue::httpd_${HTTPD_LIB_VERSION}_x::servlet::ApacheConfigFilter
libApache${HTTPD_LIB_VERSION}_Servlet.so.1
Configuration
ServerConfig
- Type: string
- Usage Constraints: optional
- Specifies Apache directives on a global level. The configured value is set in the server section of the generated Apache configuration.
HostConfig
- Type: string
- Usage Constraints: optional
- Specifies Apache directives on a virtual host level. The configured value is set in the host section of the generated Apache configuration. The Host tag and the Connector tag in the navajo.xml file must have the same value for the name attribute. Otherwise, the filter will not work as expected.
LocationConfig
- Type: string
- Usage Constraints: optional
- Adds Apache directives on location. The configured value is set in the location configurations of the generated Apache configuration. The URI of the location configurations is determined by the configured filter mapping of the ApacheConfigFilter.