Alex Rousskov wrote:
That seems likely, however the comments about the patch seem to imply
that drweb ICAP server does send "Connection: close". Here is a quote:
if ICAP daemon does not support persistent connection and
answers with 'Connection: Close' squid can stop receiving the
docum
On Mon, 2005/04/04 (MDT), <[EMAIL PROTECTED]> wrote:
Have you tried asking drweb folks whether there is something Squid can
do to prevent them from closing the connection?
No I did not.
But the DRweb team had post a patch to squid mailing list
(http://www.mail-archive.com/squid-dev@squid-cache
Alex Rousskov wrote:
FWIW, the above drweb behavior is compliant with ICAP. Conection:
keep-alive
does not (and cannot) guarantee that the connection will remain open
after
the ICAP response is sent.
OK.
Not using persistent connections with a given ICAP server would also
be compliant with ICAP.
On Sun, 2005/03/20 (MST), <[EMAIL PROTECTED]> wrote:
drweb-icap server responce with Conection:keep-alive but then
imediatelly closes the connection
OK, drweb-icap breaks the ICAP protocol here
FWIW, the above drweb behavior is compliant with ICAP. Conection:
keep-alive
does not (and cann
On Sun, 20 Mar 2005, Tsantilas Christos wrote:
OK, drweb-icap breaks the ICAP protocol here but if we have a
configuration parameter (e.g icap_keepalive) which tells to squid's icap
client to always closes the connection after a request we can overcome
these problems with such servers.
Is this
Hi all,
Squid's icap client is not perfect but it was not always responsilbe
for all problems when works with icap servers. I am testing it with
drweb-icap server. All thinks looks good, except the keep-alive behaviour.
drweb-icap server responce with Conection:keep-alive but then imediatelly
cl
