We just upgraded from 4.2.1.1 to 5.3.0 and noticed rather than seeing
ERR_UNKNOWN/ only for 3xx/4xx/5xx codes, we're now seeing
ERR_UNKNOWN/200 on every request.  Config file is unchanged

The page gets served (forward proxy) and it doesn't look like there's
any other major side-effect except the access logs are exploding since
every 200 is getting logged.

Any pointers on how to stop logging ERR_UNKNOWN/200 are appreciated.

-J

Reply via email to