>Number: 2090 >Category: mod_log-any >Synopsis: LogFormat directives are not "inherited" >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Apr 20 23:30:01 PDT 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3b6 >Environment: UNIX >Description: I had an httpd.conf file containing lines ordered:
LogFormat "...blah..." nickname . . . <VirtualHost 10.0.0.1> CustomLog filename nickname . . What happens is that the nickname is not expanded to reference the previous LogFormat nickname. Examination of the documentation is UNCLEAR about this but would seem to indicate that as most directives, this one if defined in a more global scope in the configuration file, should apply to the VirtualHosts. This seems to be a scoping issue here. >How-To-Repeat: Oh yes...easy >Fix: I'm in favor of a code fix to allow LogFormat statements to be carried globally and apply (if not redefined) within a lower VirtualHost section >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
