# Gitweb - caching

4 messages from 2006-12-31 to 2006-12-31. Participants: J.H., Robert Fitzsimons, Jeff Garzik, Jakub Narebski.
Thread: https://gitlist.dev/t/6177

## J.H., 2006-12-31 10:30

Subject: Gitweb - caching
Message-ID: <45979136.3070901@eaglescrag.net>
URL: https://gitlist.dev/e/45979136.3070901%40eaglescrag.net

```
There has been some recent discussion concerning the amount of resources
that gitweb is chewing through, particularly on kernel.org.  I've just
pushed a small set of changes out to kernel.org that add in caching to
the gitweb thats running on it.  Changes are published at
git://git.kernel.org/pub/scm/git/warthog9/gitweb.git

Thoughts or comments are welcome.

- John 'Warthog9'

```

## Robert Fitzsimons, 2006-12-31 17:41

Subject: Re: Gitweb - caching
Message-ID: <20061231174123.GI6558@localhost>
URL: https://gitlist.dev/e/20061231174123.GI6558%40localhost
In-Reply-To: <45979136.3070901@eaglescrag.net>

```
> Thoughts or comments are welcome.

Interesting work, John.  Some initial comments:

* It's a very intrusive set of changes.
* An infinite expiry date isn't valid for all pages.
* The other HTTP headers can change depending on the page returned.
* A single cache directory is going to have problems as the number of
  cached files grows.

What are the benefits of doing this inside of gitweb instead of using
something like mod_cache or mod_perl handlers?

Robert

```

## Jeff Garzik, 2006-12-31 20:01

Subject: Re: Gitweb - caching
Message-ID: <4598171D.2040002@garzik.org>
URL: https://gitlist.dev/e/4598171D.2040002%40garzik.org
In-Reply-To: <20061231174123.GI6558@localhost>

```
Robert Fitzsimons wrote:
>> Thoughts or comments are welcome.
> 
> Interesting work, John.  Some initial comments:
> 
> * It's a very intrusive set of changes.
> * An infinite expiry date isn't valid for all pages.
> * The other HTTP headers can change depending on the page returned.
> * A single cache directory is going to have problems as the number of
>   cached files grows.
> 
> What are the benefits of doing this inside of gitweb instead of using
> something like mod_cache or mod_perl handlers?

Or wrapping the gitweb output inside cgicache:
http://linux.yyz.us/projects.html

	Jeff

```

## Jakub Narebski, 2006-12-31 20:52

Subject: Re: Gitweb - caching
Message-ID: <en97tp$kc1$1@sea.gmane.org>
URL: https://gitlist.dev/e/en97tp%24kc1%241%40sea.gmane.org
In-Reply-To: <20061231174123.GI6558@localhost>

```
Robert Fitzsimons wrote:

> * An infinite expiry date isn't valid for all pages.

An infinite expiry date is not valid at all. IIRC HTTP defines that
"infinite" expiry is one year.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

```