Bug 53923 - Overriding CustomLog directive seems impossible
Summary: Overriding CustomLog directive seems impossible
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_log_config (show other bugs)
Version: 2.2.22
Hardware: All FreeBSD
: P2 minor with 5 votes (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2012-09-23 16:13 UTC by Jakob
Modified: 2018-11-07 21:08 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Jakob 2012-09-23 16:13:25 UTC
My intentions are to create an installation of apache and configure it entirely in an .conf file in the Includes directory. This went well, with one exception. The CustomLog directive seems "unoverridable".

In the httpd.conf there is a line defining something like this:

  CustomLog "/var/log/httpd-access.log" combined

Changing that line to:

  SetEnvIf Request_URI ^/heartbeat dontlog
  CustomLog "/var/log/httpd-access.log" combined env=!dontlog

Will yield the effect I am after, however chancing that line to:

  CustomLog "/var/log/httpd-access.log" combined
  SetEnvIf Request_URI ^/heartbeat dontlog
  CustomLog "/var/log/httpd-access.log" combined env=!dontlog

Does not yield the effect I am after.

I conclude that the CustomLog directive cannot be overridden, which I expected to be able to.
Comment 1 kballou+asfbugzilla 2017-03-29 21:11:49 UTC
Necro-bump: I'm seeing this behaviour in 2.4.10 and would define this as "surprising".
Comment 2 kballou+asfbugzilla 2017-03-29 21:12:34 UTC
Necro-bump: I'm seeing this behaviour in 2.4.10 and would define this as "surprising".
Comment 3 William A. Rowe Jr. 2018-11-07 21:08:54 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.