Hello, using squid-2.5.STABLE1-63 or squid-2.5.STABLE4-0
When using windowsupdate.microsoft.com with direct configuration, IE5.5, all runs smooth.
When using windowsupdate.microsoft.com with cache_peer (also squid with same version/build, verified with 2.5.STABLE1 and 2.5.STABLE4) then, after pressing "search for updates", nothing happens till doomsday.
Set up a testenvironment cause with my ISP running something other than squid I got the same problem.
But even with a squid as parent-cache the problem is there.
Therefore I think it's a problem with the setup of my squid-proxy-configuration.
squid set up in testing environment not to cache anything related to windowsupdate.
---- snip ----
cache_peer mypeer.mydomain.com parent 3128 0 no-query no-digest no-netdb-exchange no-delay
acl QUERY urlpath_regex cgi-bin \? acl MSUPDATE dstdomain windows.com windowsupdate.microsoft.com no_cache deny QUERY no_cache deny MSUPDATE
acl localiprange dst 192.168.0.0/255.255.0.0 acl mylocalapache dst 127.0.0.1/255.255.255.255 acl FTPdirect proto FTP always_direct allow localiprange always_direct allow mylocalapache never_direct allow all never_direct allow FTPdirect
---- snap ---
Someone out there knowing why windowsupdate over two proxies will not function correctly?
greetings from germany ES
