Hello!
I will check it on live system.
BTW, why does %{c}L not documented?
2016-03-29 19:31 GMT+06:00 Eric Covener <covener@xxxxxxxxx>:
> On Fri, Nov 13, 2015 at 2:54 AM, Kurtis Rader <krader@xxxxxxxxxxxxx> wrote:
>>> In my error log i get this:
>>> [Tue Nov 03 02:55:33.635958 2015] [VjiEkn8AAAEAAHuBfzkAAABB] [-:error]
>>> [pid 31617:tid [client IP:PORT] PHP Warning:
>>> unlink(/tmp/file_name.txt): No such file or directory in
>>> /var/www/file_test.php on line 1, referer REFERER
>>>
>>> If i try to find this ID in access logs - nothing found.
>>>
>>> If i search request by referer, pid, ip and port combination - there
>>> is also no ID
>>
>>
>> I tested this on my system. The value logged by %L in the access log cannot
>> be found in the error log. The %L value is clearly a hash of some sort
>> (e.g., SHA1 value of the incoming IP address and port) converted to ASCII.
>> This looks like a bug to me.
>
> The particular error log entry looks like it might not pass the
> request object, just the connection object.
>
> The mod_log_config code seems to accept %{c}L for the connection-level
> log ID. Does that match for you?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|