Re: [squid-users] Error in cache.log

On Sat, 20 Dec 2003, ads squid wrote:

> 2003/12/20 22:28:42| parseHttpRequest: Unsupported
> method 'recipientid=99&sessionid=8119^M
> ^M
> '
> 2003/12/20 22:28:42| clientReadRequest: FD 33 Invalid
> Request
> 2003/12/20 22:28:42| parseHttpRequest: Unsupported
> method 'recipientid=100&sessionid=8119^M
> ^M
> '
> 2003/12/20 22:28:42| clientReadRequest: FD 33 Invalid
> Request

The above looks like a client sending invalid POST requests, sending more
data than claimed in the request headers.

> 2003/12/21 10:04:13| clientReadRequest: FD 16 Invalid
> Request
> 2003/12/21 10:05:00| clientReadRequest: FD 14 Invalid
> Request
> 2003/12/21 10:05:04| clientReadRequest: FD 14 Invalid
> Request
> 2003/12/21 10:05:04| clientReadRequest: FD 14 Invalid
> Request
> 2003/12/21 10:05:04| clientReadRequest: FD 14 Invalid
> Request
> 2003/12/21 10:05:04| clientReadRequest: FD 16 Invalid
> Request
> 2003/12/21 10:09:11| clientReadRequest: FD 14 Invalid
> Request

Was there no other log entries between these?

> Then I reconfigure squid and agin it starts working
> Any clue what should be done to stop this.

Try to find the offending client and what it is doing. A good start is the
time these occurs and matching these to activity in access.log. Each of
these messages should also have one line in access.log with a status code
of 400 and a blank hierarchy code, and most likely no URL, so it should
not be very hard to find who is causing these.

Regards
Henrik
Received on Sun Dec 21 2003 - 07:27:48 MST