Henrik Nordstrom wrote:
>
> I had fogot about this issue. I'll note this issue so it is not
> forgotten again. Needs to be fixed to not use MSG_PEEK so it can wait
> for more data to arrive via commSetSelect(), which involves some magic
> to get the interactions with the main Squid code correct.
mån 2003-06-23 klockan 14.17 skrev Geetha Manjunath:
> Yes, you are right here - but this case would probably show up only with
> buggy ICAP servers that do not end ICAP headers with \r\n\r\n . The rest
> of code catches this error. Actually it signals an HTTP internal error
> rather than the sugg
Thanks for forwarding this, Henrik.
Hello Larry,
Sorry for this delayed reply..
> -Original Message-
> From: Rosenbaum, Larry M.
.
>
> 1) (icap.c) There is a problem with the way icapRespModReadReply()
> tries to read the ICAP header without reading past the header. The
>
On Tuesday 10 June 2003 11.37, ralf wrote:
> I think the real problem is that some pointers are not reset
> properly. Here is a patch:
>
> diff -u -r1.38.6.11.2.2 cache_cf.c
> --- cache_cf.c 7 Apr 2003 13:28:50 - 1.38.6.11.2.2
> +++ cache_cf.c 10 Jun 2003 09:03:00 -
> @@ -2145,6 +2
Hello Henrik,
on Mon, 09 Jun 2003, Henrik Nordstrom wrote:
> -Original Message-
> From: Rosenbaum, Larry M.
> Sent: Thursday, June 05, 2003 12:57 PM
> To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: Squid ICAP client problems
[...]
> 2) (cache_cf.c) If you don't have a "icap_c
-- Forwarded Message --
Subject: FW: Squid ICAP client problems
Date: Mon, 09 Jun 2003 14:35:27 -0400
From: "Rosenbaum, Larry M." <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Could you please forward this to the Squid ICAP developers, or tell
me whom to contact?
Thanks, Larry
--
