Hi,
Other places of the code also seem to log message in the same kind of
condition at either APLOG_DEBUG, APLOG_ERR or APLOG_INFO level.
Should they be updated as well?
The following use APLOG_DEBUG:
./server/core.c:4622
ap_pass_brigade_fchk()
./modules/isapi.c
./modules/filters/mod_ext_filter.c:880
./modules/filters/mod_reflector.c:157
The following use APLOG_ERR:
./modules/arch/netware/mod_nw_ssl.c:1201
./modules/generators/mod_cgid.c:1651
./modules/generators/mod_asis.c:100
./modules/test/mod_dialup.c:84
./modules/proxy/mod_proxy_wstunnel.c:289
./modules/proxy/proxy_util.c:3571
./modules/proxy/mod_proxy_connect.c:171
./modules/proxy/mod_proxy_fdpass.c:211
The following use APLOG_INFO:
./modules/echo/mod_echo.c:179
./modules/http/http_filters.c:1617
Best regards,
CJ
Le 09/08/2014 23:20, cove...@apache.org a écrit :
Author: covener
Date: Sat Aug 9 21:20:50 2014
New Revision: 1617018
URL: http://svn.apache.org/r1617018
Changes with Apache 2.5.0
+ *) mod_ratelimit: Drop severity of AH01455 and AH01457 (ap_pass_brigade
+ failed) messages from ERROR to TRACE1. Other filters do not bother
+ re-reporting failures from lower level filters. PR56832. [Eric Covener]
+
