Hello Benno, Bob,

I've added this item to our "todo/wishlist" page (#28):
  http://savannah.gnu.org/maintenance/SavannahHackingIdeas/

Since there's not much else for us to do in the short term about this,
I'm closing this ticket for now.

regards,
 - assaf

Yes, server-side caching is good -- I wasn't suggesting to disable caching.  But it becomes a problem when I look at one page, upstream does a push, I look at another page of the same repo, which has the new content, I go back to the earlier page, but it still shows the old situation.  This is puzzling and confusing.

What would be nice to have is: that cgit invalidates the cache for a certain repo whenever something is pushed to that repo.  This may be too hard to make, though, I don't know.

An alternative might be that whenever cgit receives a request for a page, it checks whether there has been a push to the relevant repo since the page was cached, and only if not, it serves the cached page.  This might be too hard to make, too, though.

Since a few days, looking at cgit pages on Savannah can result in a mismatch when in the meantime a push happened.

For example, I looked at http://git.savannah.gnu.org/cgit/nano.git/log/, then did a push, did a reload in my browser -- no effect.  (This always worked until a few days ago.)  But if I then look at http://git.savannah.gnu.org/cgit/nano.git/commit/, for example, the last commit is there.  But then going back to http://git.savannah.gnu.org/cgit/nano.git/log/, the last commit is still missing.  Another reload does not help.  Only when waiting for five minutes and then doing a reload again, things will finally match.

Of course, this is a minor issue, because how often will it happen that a user is browsing through cgit just when upstream does a push?  But when it does happen... it can be rather confusing.