www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject Re: mod_log-any/9574: unexpected behaviour of CustomLog directive
Date Sat, 26 Jan 2002 18:35:17 GMT
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: unexpected behaviour of CustomLog directive

State-Changed-From-To: open-analyzed
State-Changed-By: slive
State-Changed-When: Sat Jan 26 10:35:17 PST 2002
State-Changed-Why:

Your solution will not work because the CostumLog directive
does not need to use a defined nickname.  Instead, it can
use an explicit logformat string.  Since literal characters
are allowed in a logformat string, apache is perfectly
happy with the format string "ssl-format" or whatever.

One solution might be to issue a warning if there is not
at least one "%" directive in the format string.  It is
highly unlikely that anyone wants to have a log with only
literals.



Mime
View raw message