On Mon, Jan 19, 2015 at 08:32:07AM +0100, Volker Grabsch wrote:
> I agree that the right solution is to:
>
> (1) log invalid request names only on 400 ("Bad Request") responses
I don't know why do you think so.
> (2) make AWstats deal with at least these log lines
>
> I'm aware that (2) is cove
Package: awstats
Followup-For: Bug #706076
Both workarounds,
- Use NbOfLinesForCorruptedLog in awstats
- Adopt apache log configuration to hide such messages
have problematic side effects. I agree that the right solution is to:
(1) log invalid request names only on 400 ("Bad Request") response
Package: awstats
Version: 6.9.5~dfsg-5
Severity: important
Please ignore the missing config files, I'm using another names to them.
For some days, Awstats stopped logging a lot of data, and I discovered the
problem: I'm using LogRotate, and frequently the first line of my log files
is something
3 matches
Mail list logo