On Mon, 2 May 2005, Aldebaran wrote:
Not at all, for example this transaction,
192.168.0.24 - - [29/Apr/2005:15:53:05 +0200] "HEAD http:// www.download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/ windowsxp-kb890175-x86-express-ita_36ad15fcf3ed7ef0dc1a04d5706bfea0ac4efaeb.exe HTTP/1.1" 200 523 TCP_HIT:NONE [Accept: */*\r\nAccept-Encoding: identity\r\nUser-Agent: Microsoft BITS/6.6\r\nHost: www.download.windowsupdate.com\r\nProxy-Connection: Keep-Alive\r\n] [HTTP/1.1 200 OK\r\nDate: Tue, 26 Apr 2005 21:56:34 GMT\r \nContent-Length: 337640\r\nContent-Type: application/octet-stream\r \nETag: "928113fd6af7c41:b45"\r\nLast-Modified: Mon, 10 Jan 2005 23:20:35 GMT\r\nAccept-Ranges: bytes\r\nServer: Microsoft-IIS/6.0\r \nX-Powered-By: ASP.NET\r\nP3P: CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"\r\nConnection: keep-alive\r\n\r]
This is a HEAD request, not retreiving any data at all (only headers).
192.168.0.24 - - [29/Apr/2005:15:53:05 +0200] "GET http:// www.download.windowsupdate.com/msdownload/update/v3-19990518/cabpool/ windowsxp-kb890175-x86-express-ita_36ad15fcf3ed7ef0dc1a04d5706bfea0ac4efaeb.exe HTTP/1.1" 200 338163 TCP_HIT:NONE [Accept: */*\r\nAccept-Encoding: identity\r\nUser-Agent: Microsoft BITS/6.6\r\nHost: www.download.windowsupdate.com\r\nProxy-Connection: Keep-Alive\r\n] [HTTP/1.1 200 OK\r\nDate: Tue, 26 Apr 2005 21:56:34 GMT\r \nContent-Length: 337640\r\nContent-Type: application/octet-stream\r \nETag: "928113fd6af7c41:b45"\r\nLast-Modified: Mon, 10 Jan 2005 23:20:35 GMT\r\nAccept-Ranges: bytes\r\nServer: Microsoft-IIS/6.0\r \nX-Powered-By: ASP.NET\r\nP3P: CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"\r\nConnection: keep-alive\r\n\r]
And this is the acual request. Retreiving an exe file of 337640 bytes.
Both were cache misses.
And there was not a single second request for this same object in your trace.
was cached but had one problem: the dimension of object in cache and dimension in HTTP download is different. In this case the client receive only 338163 byte from squid cache and download the end of file from internet. In squid cache I have 330-350 KB sizes .exe objects from windowsupdate and files can be really 5 MB sizes. If I can store this files completely, I resolve a great problem in my net (16 clients with ISDN 64Kb connection).
This is a completely different question than the original question which claimed the situation was a lot worse when using Squid than when not.
You ask if you can use Squid to cache windows update, and the answer is that you would have been able if Microsoft had wanted this to be possible. Unfortunately Microsoft does not seem too keen on making Windows update cache friendly, and each new release of Windows Update is increasingly more unfriendly to caches, making life increasingly difficult for people with low bandwidth connections.
Regards Henrik
