On 12/9/06, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
Perhaps gitweb should generate it's own ETag instead of messing with 'expires' header?
That'll be the winning solution. A combination of - cache SHA1-based requests forever - cache ref-based requests a longish time, setting an ETag that contains headname+SHA1 - on 'revalidate', check the ETag vs the ref and only recompute if things have changed In the meantime, the code on kernel.org needs to be updated to the latest gitweb. On our server, I'd say the newer gitweb is 3~4 times faster serving the "expensive" summary pages. And much smarter in terms of caching headers. cheers martin - 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