Am 07.02.2013 14:22, schrieb Dennis Jacobfeuerborn: >> with the old behavior it was easy to grep thrugh 404 errors >> of any vhost and find broken images in CSS files and so on > > Why can't you grep/awk through the access log files the same way you > grep/awk through the error logs? Just because there's more than one log file?
exactly >> in my opinion of someone breaks the logging-behavior he should >> implement a "Error404Log" at the same time or leave it as it >> was for decades >> > > Just because the new behavior isn't to your liking doesn't mean its > "broken". I for one welcome this change greatly. The "Error404Log" idea > isn't all that bad but a bit limited. If such a thing were implemented I > would rather like to see something like a "ContentErrorLog" that also > contains denied access and other errors that prevent content from being > delivered. +1 for ContentErrorLog i have only a problem with the need for scripts to grep around all vhosts and they need their own access-log for usages
signature.asc
Description: OpenPGP digital signature
