Re: [squid-users] Problem talking ICAP to McAfee Web Gateway

2016-05-20 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The problem is always with the DNA. The main question - by whom;) 21.05.16 0:41, Rob Worsnop пишет: > Quick update: The problem isn't with Squid. > > When MWG decides it wants to send an early response, it seems it also > decides to send garbage

Re: [squid-users] Problem talking ICAP to McAfee Web Gateway

2016-05-20 Thread Rob Worsnop
Quick update: The problem isn't with Squid. When MWG decides it wants to send an early response, it seems it also decides to send garbage data after a few KB of valid data. Squid notices that MWG is trying to send a chunk bigger than advertised and promptly closes the connection. On Wed, May 18,

Re: [squid-users] Problem talking ICAP to McAfee Web Gateway

2016-05-18 Thread Alex Rousskov
On 05/18/2016 03:56 PM, Rob Worsnop wrote: > In certain circumstances, MWG will start streaming the RESPMOD response > before Squid has finished sending all the chunks in the RESPMOD request. > > Squid does not like this. If Squid does not like this, it is a Squid bug IMO. > As far as I can te

[squid-users] Problem talking ICAP to McAfee Web Gateway

2016-05-18 Thread Rob Worsnop
I'm having a problem talking ICAP with McAfee Web Gateway (MWG). In certain circumstances, MWG will start streaming the RESPMOD response before Squid has finished sending all the chunks in the RESPMOD request. Squid does not like this. It seems to interpret the arrival of response traffic as a s