On Sat, 2005-06-04 at 13:26 +0300, Junix Gaspar wrote: > Inshort, it seems that the update file is being downloaded again in > the from the site and it is not cached in the PRoxy server. >
Have you tried looking at the cache directory to verify your claim? I have implemented a SQUID server before, and it does cache the update requests. However, the problem lies with the request construction to be able to retrieve the chached objects from the SQUId server. Since URL's vary from one update request to another, retrieving the objects would mean that two requests should have the exact same URL to retrieve a cached object. And that rarely happens with Windows update since it looks like it requires and creates a session ID everytime an update is requested. > My questions are: > > 1. Is it because I need to modify somethin in my proxy? You can modify something in your proxy (perhaps making sure that the setting for the maximum cached object size is greater than a certain number to ensure that even large objects would be cached). That makes sure that the objects are cached, but not necessarily that they will be retrieved on subsequent requests for the same object using a different URL. But if you just want it cached, it would most probably be cached. :D > 2. Is it because http://updates.m$.com doesn't allow that (program > updates) to be cached? It can be in the headers, but I think you can ignore those "do not cache" headers -- breaking compliance to HTTP specifications. > 3. is because the whole transaction is encrypted and therefore not > cached in the proxy server? or somehow cached but because its > encrypted it does not give it to other transaction because its another > session? Please do tel us if you find out whether or not this is the case. > 4. ? > > And yes, we do have a repository of all the bells and whistles > (windows update) in our file server. it just that I want to understand > why its not caching? > > thanks, > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph -- Dean Michael Berris <[EMAIL PROTECTED]> _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
