Nick Kew writes:
That suggests the request headers exceeded a hard limit in the server (and
very possibly that it was a malformed request). The size of the request is
irrelevant UNLESS something is broken, like the headers never being
terminated. Setting your loglevel to debug or sniffing the request on the
wire might tell you more, if perhaps you can identify where it's coming from
to set up a test case.
I turned on debugging and this is what I got:
[Thu Sep 08 13:07:19 2005] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Thu Sep 08 13:10:10 2005] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Thu Sep 08 13:10:10 2005] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Thu Sep 08 13:13:14 2005] [error] [client 80.223.254.148] request failed:
error reading the headers, referer:
http://vuodatus.net/site/control/editblog
[Thu Sep 08 13:13:37 2005] [info] (104)Connection reset by peer:
core_output_filter: writing data to the network
[Thu Sep 08 13:13:37 2005] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Thu Sep 08 13:14:47 2005] [info] (104)Connection reset by peer:
core_output_filter: writing data to the network
The "error reading headers" is there, but there is no other error message
that matches the time. The Connection reset by peer and Broken pipe are, at
least according to Google search results, results of Apache2 + PHP
combination and seem to be harmless.
Tuomas Rinta
---------------------------------------------------------------------
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]
