Because mod_access_compat directives take precedence over the mod_authz_host one in this configuration merge scenario. This example conversely works as expected: Mixing old and new directives: WORKING AS EXPECTED section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. FilesMatch ".*" matches and another merge opportunity arises, causing the CustomHeaderName

Because mod_access_compat directives take precedence over the mod_authz_host one in this configuration merge scenario. This example conversely works as expected: Mixing old and new directives: WORKING AS EXPECTED section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. FilesMatch ".*" matches and another merge opportunity arises, causing the CustomHeaderName

section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. FilesMatch ".*" matches and another merge opportunity arises, causing the CustomHeaderName deprecated, etc.. This is true for .htaccess too since they have the same priority as Directory in the merge order. The important concept to understand is that configuration sections like Directory and FilesMatch

takes. A later configuration section with directives from a given module might cause a conceptual "merge" of some direc- tives, all directives, or a complete replacement of the modules configuration with environment variables all existed for the request): Header merge Cache-Control no-cache env=CGI Header merge Cache-Control no-cache env=NO_CACHE Header merge Cache-Control no-store env=NO_STORE then the response would contain the following header: Cache-Control: no-cache, no-store If append was used instead of merge, then the response would contain the following header: Cache-Control: no-cache, no-cache, no-store

takes. A later configuration section with directives from a given module might cause a conceptual "merge" of some direc- tives, all directives, or a complete replacement of the modules configuration with environment variables all existed for the request): Header merge Cache-Control no-cache env=CGI Header merge Cache-Control no-cache env=NO_CACHE Header merge Cache-Control no-store env=NO_STORE then the response would contain the following header: Cache-Control: no-cache, no-store If append was used instead of merge, then the response would contain the following header: Cache-Control: no-cache, no-cache, no-store

Because mod_access_compat directives take precedence over the mod_authz_host one in this configuration merge scenario. This example conversely works as expected: Mixing old and new directives: WORKING AS EXPECTED section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. FilesMatch ".*" matches and another merge opportunity arises, causing the CustomHeaderName

Because mod_access_compat directives take precedence over the mod_authz_host one in this configuration merge scenario. This example conversely works as expected: Mixing old and new directives: WORKING AS EXPECTED section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. FilesMatch ".*" matches and another merge opportunity arises, causing the CustomHeaderName

Because MOD ACCESS COMPAT directives take precedence over the MOD AUTHZ HOST one in this configuration merge (p. 35) scenario. This example conversely works as expected: Mixing old and new directives: WORKING section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. • FILESMATCH ".*" matches and another merge opportunity arises, causing the

Because MOD ACCESS COMPAT directives take precedence over the MOD AUTHZ HOST one in this configuration merge (p. 35) scenario. This example conversely works as expected: Mixing old and new directives: WORKING section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. • FILESMATCH ".*" matches and another merge opportunity arises, causing the

section matches too, then each module with a directive in either of the sections is given a chance to merge its configuration between the two sections. The result is a third configuration, and the process goes its code to override in case of a merge, a new configuration is created to set the CustomHeaderName header with the value two. FilesMatch ".*" matches and another merge opportunity arises, causing the CustomHeaderName deprecated, etc.. This is true for .htaccess too since they have the same priority as Directory in the merge order. The important concept to understand is that configuration sections like Directory and FilesMatch