In the README, there is a CustomLog directive, which does nothing if VirtualHosts with other CustomLog directives active. This gives the false impression that mod_brotli does not work, since the log file is present, but nothing will ever get logged for affected VirtualHosts.
This is especially true for distributions like Ubuntu where the modules are pre-loaded globally and the configuration section is copied to a module-related configuration file.
Apache >= 2.4.19 has added a GlobalLog directive for this purpose, but is not yet present in most current distributions.
Therefore, the apache-mod-brotli documentation should note that the CustomLog directive must be moved to the VirtualHost section in order to work.
In the README, there is a CustomLog directive, which does nothing if VirtualHosts with other CustomLog directives active. This gives the false impression that mod_brotli does not work, since the log file is present, but nothing will ever get logged for affected VirtualHosts.
This is especially true for distributions like Ubuntu where the modules are pre-loaded globally and the configuration section is copied to a module-related configuration file.
Apache >= 2.4.19 has added a GlobalLog directive for this purpose, but is not yet present in most current distributions.
Therefore, the apache-mod-brotli documentation should note that the CustomLog directive must be moved to the VirtualHost section in order to work.