Re: [squid-users] delivering stale content while fetching fresh
Henrik Nordstrom schrieb: See the current STABLE release. (2.6). Squid-3 is still under development and not all features of 2.6 is available in Squid-3 yet. I checked out squid 2.6 STABLE and I found the feature in question and the associated comment in the squid.conf file. Thank you. Please correct me, if I'm wrong assuming that: * refresh_stale_hit makes stale content (within the refresh_stale_hit-defined period) to be accessed, while - in this moment - the fresh content is fetched from the backend servers to be cached * refresh_stale_hit is independent of collapsed_forwarding, i.e. it doesn't matter wether collapsed_forw. is enabled or not * collapsed_forwarding bundles concurrent request for the same URI into one; but what means concurrent? Within a certain time slot? If yes, how long is this time slot? Thanks a lot, Gregor.
Re: [squid-users] delivering stale content while fetching fresh
Henrik Nordstrom schrieb: Gregor Reich schrieb: * refresh_stale_hit makes stale content (within the refresh_stale_hit-defined period) to be accessed, while - in this moment - the fresh content is fetched from the backend servers to be cached Correct. It means that only one client will wait for the refresh, the others will get the stale copy. Please tell me: is there any possibility to have this client also being served with the stale content instead of waiting for the fresh one? Thanks, Gregor. Mit freundlichen Grüssen Gregor Reich -- Jud Grafik+Internet Grynaustrasse 21 8730 Uznach Tel. 055 290 16 59 Fax 055 290 16 26 Skype: gregreich (Internettelefonie www.skype.com) www.juhui.ch
Re: [squid-users] delivering stale content while fetching fresh
Henrik Nordstrom schrieb: tor 2006-08-31 klockan 16:14 +0200 skrev Gregor Reich: But is there a possibility to have squid responding - to a client that request a document that is (in some way) expired - with the stale document while - at the same time fetching the new one and storing it to cache: ready to deliver to the next requesting client. Kind of. See the collapsed_forwarding and refresh_stale_hit options. Thank you for the hint; I searched the archives, googled and searched squid.conf (Squid3) but I didn't found any description of these options (what do they do, how to configure, possible pitfalls and so on). Can anyone -possibly Hendrik - give me a hint where to look? (In the source code of course; but I'm not really able to do so...) Thanks, Gregor. -- Jud Grafik+Internet Grynaustrasse 21 8730 Uznach Tel. 055 290 16 59 Fax 055 290 16 26 Skype: gregreich (Internettelefonie www.skype.com) www.juhui.ch
[squid-users] delivering stale content while fetching fresh
Hi all I'm looking for a reverse proxy solution for a dynamic website, where page generation is where ressource intensive and therefore slow (even if there's no heavy load on the servers, i.e. where minimal generation time is high). Know this website is fairly dynamic an caches would have to be updated at least every 10 minutes. And as I've read, squid stores it's cache content table in md5 and can't therefore update it's cache content without having a request from a client giving its explicit URL. But is there a possibility to have squid responding - to a client that request a document that is (in some way) expired - with the stale document while - at the same time fetching the new one and storing it to cache: ready to deliver to the next requesting client. This would prevent any client from waiting for a page being generated because it's stale and still having dynamic content. Thank you for replying! Regards, Gregor. Mit freundlichen Grüssen Gregor Reich -- Jud Grafik+Internet Grynaustrasse 21 8730 Uznach Tel. 055 290 16 59 Fax 055 290 16 26 Skype: gregreich (Internettelefonie www.skype.com) www.juhui.ch
