On Sun, 10 Dec 2006, Jakub Narebski wrote: > > Well, the idea (perhaps stupid idea: I don't know how caching engines > / reverse proxy works) was that there would be caching engine / reverse > proxy in the front (Squid for example) would cache results and serve it > to rampaging hordes. Sure, if the proxies actually do the rigth thing (which they may or may not do) > What about the other idea, the one with raising expires to infinity for > immutable pages like "commit" view for commit given by SHA-1? Even if > the clients won't cache it, the proxies and caches between gitweb and > client might cache it... I agree, but as mentioned, I think the _real_ problem tends to be the pages that don't act that way (ie summary pages, both at the individual project level and the top "all projects" level). Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html