expires header in bugdb

[Marc Slemko <ma...@worldgate.com>]

Why was this added?  Someone said something about their client reloading
the page each time they scrolled(!?!?)  That seems like a pretty broken
client to me.

Using Navigator3, it was fine for me before and when I wanted an update I
just reloaded it now.  Now, when I have the index up, it keeps reloading
it because it expires.  eg. if I load the index, look at a PR, go away for
30 minutes, go back to the index, it reloads it.  I find that quite
annoying.

Re: expires header in bugdb

[Dirk-Willem van Gulik <di...@elect6.jrc.it>]

On Sat, 15 Nov 1997, Marc Slemko wrote:

> Why was this added?  Someone said something about their client reloading
> the page each time they scrolled(!?!?)  That seems like a pretty broken
> client to me.

Hmm, actually it was resizing and back/forward. And yes, I use netscape
3... that should be broken enough. Originally I wanted to add a Last-
Modifed; but I could not see a way of getting that out of the database,
so I proposed a patch for an expiry of 30 minutes. (Which is about
20 minutes more than it takes do download the page in switzerland
around 13GMT :-)

Seems this needs one more itertation; as the form now also reloads
itself; it could have a longer TTL. Any other cache pragma's one
cann set ?

Dw.