httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <wr...@rowe-clan.net>
Subject Re: Error log format configuration syntax
Date Wed, 21 Jul 2010 22:00:12 GMT
On 7/21/2010 4:35 PM, Stefan Fritsch wrote:
> On Wednesday 21 July 2010, William A. Rowe Jr. wrote:
>> On 7/20/2010 2:14 PM, Stefan Fritsch wrote:
>>>> - taking all adjacent non-whitespace as prefixes and suffixes,
>>>> collapse resulting adjacent whitespace in the output by adding
>>>> the whitespace in front of the prefix to the prefix and
>>>> dropping leading whitespace from the resulting line)
>>>
>>> ErrorLogFormat "[%{u}t] [%l] [pid %P^:tid %T^] ^%F: ^%E: ^[client
>>> %a] ^%M ^, referer: %{Referer}i"
>>
>> Outch - please evaluate using %^xxx instead.  I'd rather this were
>> simply supported in a unified logging formatter, so it would apply
>> to access, new log extensions, etc.  It could imply
>> delete-adjacent non-whitespace unless there were multiple
>> %-escapes in the same token.
>>
>> I'm not fond of arbitrarily adding new escape codes, and we already
>> had a suitable one (%).
> 
> We want a dedicated field separator, because only deleting adjacent 
> non-whitespace wouldn't work for things like "[client %a]". I would 
> prefer a single character as separator and have chosen '^' because it 
> is relatively unlikely to appear literally in the log format. But I 
> wouldn't mind using a two character separator. In this case, '%|' is 
> probably more readable than '%^'.

Two thoughts ... some %{[client }q text-literal quoting method could keep
that as a literal space, not whitespace.  Or perhaps [client\ %^a] could
do the same thing?

Mime
View raw message