Re: kernel.org mirroring (Re: [GIT PULL] MMC update)

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Dec 9, 2006, 01:28 UTC
Message-ID: <46a038f90612081728s65d65ccewe64fa1a496de76fa@mail.gmail.com>
In-Reply-To: <200612081438.25493.jnareb@gmail.com>

On 12/9/06, Jakub Narebski <jnareb@gmail.com> 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

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.