On 1/03/2016 12:26 p.m., Eliezer Croitoru wrote: > Hey Ryan, > > I noticed that you are using a windows version of squid and ontop of > that a 2.X version. And on top of that it has been patched with unknown extensions. So is formally outside our ability to assist with support of this binary. > Technically this version is not supported anymore by the squid-cache > project and from the settings either you are running a very old machine > or something else not really known to me. > It's hard to know what is the difference in the request that squid does > compared to BlueCoat or other proxies without sniffing the network. > And since it's a HTTP connection it would not be very hard to find the > culprit with couple wireshark dumps. > The options I can think about are: > - squid 2 uses http/1.0 instead of http/1.1 which the service requires > - squid 2 adds something to the request that breaks the connection > - the upstream proxy(proxy1.ap.webscanningservice.com) is doing > something to the connection. > - the combination of both squid2 and the upstream complicates things and > the web application doesn't like it. > > If you do have any way to upgrade the service from 2.X to anything newer > do that instead of something else. > Try to take a look at: > http://squid.diladele.com/ > > If you do have the option to run it on a Linux machine instead of a > windows consider to do so. > > If you want me to analyze the wireshark dumps from the proxy server send > them privately. > > Eliezer > Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
