ons 2006-11-08 klockan 16:26 +0100 skrev Christophe Boyanique:
We have read enough data (27 bytes) to have all the body (as
content-length is 27), so we set the eof flag.
if (!icap-flags.reqmod_http_entity_eof)
commSetSelect(fd, COMM_SELECT_READ, icapReqModReadHttpBody,
icap,
Henrik Nordstrom a écrit :
We have read enough data (27 bytes) to have all the body (as
content-length is 27), so we set the eof flag.
if (!icap-flags.reqmod_http_entity_eof)
commSetSelect(fd, COMM_SELECT_READ, icapReqModReadHttpBody,
icap, 0);
eof in ICAP is that 0 chunk... so
Hi,
I send this mail from un account which is not subscribed to the mailing
list so I am re-sending it. Sory about that.
Please to the mailing list moderator to ingore the first mail.
-
Hi Christophe,
First of all squid3 has a better support for icap protocol now.
Maybe it is
On Thu, Nov 09, 2006, Christophe Boyanique wrote:
Note: As Adrian said most efforts is focused on the Squid-3 release,
which also includes ICAP support.
I understand that but the problem is that we have this bug in production
on heavy loaded site (we took several weeks to find it out) and
tor 2006-11-09 klockan 12:37 +0200 skrev Tsantilas Christos:
+ if (icap-chunk_size 0 )
+ icap-flags.reqmod_http_entity_eof = 1;
Shouldn't that be = 0 or maybe even == 0?
Regards
Henrik
signature.asc
Description: Detta är en digitalt signerad meddelandedel
Hi,
I think it should be icap-chunk_size == -2.
In icapParseChunkSize function in common_icap.c file the
icap-chunk_size set to -2 when the 0\r\n\r\n sequence parsed
Regards,
Christos
Henrik Nordstrom wrote:
tor 2006-11-09 klockan 12:37 +0200 skrev Tsantilas Christos:
+ if
