> > I think I now understand what causes the problem. [...] > > Very interesting. Have you also been able to find out why not everyone > is having these problems? >
I've been wondering about that too. The way I see it, the problem only occurs under the following conditions: - the browser doesn't have a copy of the page in its cache - WWWOFFLE does have a copy of the page in its cache - WWWOFFLE is online - WWWOFFLE is configured to (re-)request the page - the remote server responds with code 304 (not modified). I can think of a number of situations in which you would probably not notice this problem, e.g. if your browser cache and WWWOFFLE cache have very similar contents. But in my opinion it is not in any way "system related". -- Paul A. Rombouts <[EMAIL PROTECTED]> Vincent van Goghlaan 27 5246 GA Rosmalen Netherlands
