I've noticed this on squid3 as well. While trying to hunt this, I've
found this in
HttpStateData::readReply:
...
} else if (flag == COMM_OK && len == 0 && !flags.headers_parsed) {
fwd->fail(errorCon(ERR_ZERO_SIZE_OBJECT, HTTP_BAD_GATEWAY));
eof = 1;
flags.do_next_read = 0;
tor 2006-06-29 klockan 10:40 -0300 skrev Gonzalo Arana:
> ...
> } else if (flag == COMM_OK && len == 0 && !flags.headers_parsed) {
> fwd->fail(errorCon(ERR_ZERO_SIZE_OBJECT, HTTP_BAD_GATEWAY));
[..]
> } else if (flag == COMM_OK && len == 0) {
[..]
> if (!flags.headers_parsed)
>
There's been some rebuild failures showing up in squid-2.6 when its used
with COSS and another store type (eg AUFS).
The basic reasoning is this: each storedir (aufs, diskd, ufs, and COSS
which I'm to blame for) assumes that if it sees an fresher object
during rebuild the older storeentry object i