Dear Ellezer Thank you for this. it appears the way forward would be to check that the URL matches a pattern, and if it does, compute the store_id from the checksum embedded in the URL. The same pattern might be used across a large range of windows update objects, thereby avoiding cache misses even when the same object is fetched with a significantly different URL. For example, different windows update versions, update methods and product versions. A checksum match is a guarantee the object is identical. i understand issues could arise from differing header information. I suppose it is a matter of trying it and see. On 10 April 2014 20:07, Eliezer Croitoru <eliezer@xxxxxxxxxxxx> wrote: > Hey Nick, > > In a case you do know the tokens meaning and if it is working properly you > can try to use StoreID in 3.4.X > http://wiki.squid-cache.org/Features/StoreID > > It is designed to allow you this specific issue you are sure it is. > > About the 4GB or 1GB updates it's pretty simple. > Microsoft release an update which contains "everything" about the about even > that the update for your machine is only part of the file. > This is what the last time I verified the issue. > > Also there is another side that OS become more and more complex and an > update can be really big which almost replacing half of the OS components. > > What ever goes for you from the options is fine and still I have not seen > microsoft cache solution. > How is it called? > > Eliezer > > > On 04/10/2014 08:50 PM, Nick Hill wrote: >> >> Is there a convenient way to configure Squid to do this? >> >> Thanks. > >
