After installing lusca/squid, I'm getting the following errors continuously in cache log:
2012/12/06 16:34:03| clientEatRequestBodyHandler: FD 253: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:34:03| clientEatRequestBodyHandler: FD 253: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:35:03| clientEatRequestBodyHandler: FD 62: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:35:03| clientEatRequestBodyHandler: FD 46: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:36:04| clientEatRequestBodyHandler: FD 216: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:36:04| clientEatRequestBodyHandler: FD 216: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:37:04| clientEatRequestBodyHandler: FD 382: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:37:04| clientEatRequestBodyHandler: FD 41: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:38:04| clientEatRequestBodyHandler: FD 16: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:38:04| clientEatRequestBodyHandler: FD 16: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:39:04| clientEatRequestBodyHandler: FD 98: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:39:05| clientEatRequestBodyHandler: FD 89: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:40:05| clientEatRequestBodyHandler: FD 202: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:40:05| clientEatRequestBodyHandler: FD 202: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:41:05| clientEatRequestBodyHandler: FD 145: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:41:05| clientEatRequestBodyHandler: FD 145: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:42:05| clientEatRequestBodyHandler: FD 148: no more data left in socket; but request header says there should be; aborting for now
2012/12/06 16:42:05| clientEatRequestBodyHandler: FD 148: no more data left in socket; but request header says there should be; aborting for now
How can I solve this?
