The problem probably lies in the client that issues a request which is not followed by a list of headers terminated with 2 <CR>.
You can easily reproduce this problem by telneting to the Apache server, issuing a request and let it time out. For the implementation, look at server/protocol.c -ascs -----Original Message----- From: Krist van Besien [mailto:[EMAIL PROTECTED] Sent: Thursday, July 07, 2005 12:53 PM To: users@httpd.apache.org Subject: [EMAIL PROTECTED] Error message Hello, does someone know what this means: [Wed Jul 06 15:23:18 2005] [error] [client 127.0.0.1] request failed: error reading the headers, referer: http://xxx.yyy.ch:7100/Portal?cmd=CCI&xmla Krist -- [EMAIL PROTECTED] Solothurn, Switzerland --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
