On 25 Oct 2004 06:40:08 -0000, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Index: protocol.c
> ===================================================================
> RCS file: /home/cvs/httpd-2.0/server/protocol.c,v
> retrieving revision 1.155
> retrieving revision 1.156
> diff -u -r1.155 -r1.156
> --- protocol.c 23 Oct 2004 22:39:53 -0000 1.155
> +++ protocol.c 25 Oct 2004 06:40:08 -0000 1.156
> @@ -603,7 +603,10 @@
> r->proto_num = HTTP_VERSION(1,0);
> r->protocol = apr_pstrdup(r->pool, "HTTP/1.0");
> }
> -
> + else if (r->connection->keepalive != AP_CONN_KEEPALIVE) {
> + ap_log_rerror(APLOG_MARK, APLOG_NOTICE, rv, r,
> + "request line read error.");
> + }
1.3 issues such a message only if it is a timeout error. 1.3 uses
LOGLEVEL_INFO. With LOGLEVEL_NOTICE there is no way to keep this out
of the error log.
Some users have relatively large numbers of connection-oriented
problems (I see this most often with users in SE Asia). Something
like this will result in a lot of messages for the types of conditions
they encounter on a regular basis.
Checking specifically for a timeout error (like 1.3*) and using
LOGLEVEL_INFO seems appropriate.
*In 1.3, it is the timeout handling which issues the message; I don't
see any similar messages in 1.3 mainline.
