In article <[EMAIL PROTECTED]>, Tony Moore <[EMAIL PROTECTED]> wrote:
> Maybe there's no cache problem - if there's no new build, you'll see the > same page every time. In my earlier posting, Message-ID: <[EMAIL PROTECTED]> you will see that I wrote: > Using the query string trick, I managed to have the current and previous > versions on my screen, reloadable, concurrently. Which means that there was a new version page, but the standard URL gave a reloadable version of the older page. This was/is my problem. I cannot see - unless it is a cache problem - how http://www.netsurf-browser.org/builds/ gives the old page, whilst a URL of, say, http://www.netsurf-browser.org/builds/?a=rubbish can give the current (new) page. Both consistently. I don't know how to make this any clearer. You wrote: > Maybe there's no cache problem - if there's no new build, you'll see the > same page every time. My problem is I see the same old page sometimes even when there /is/ a new one available! All I'm asking is to have the page non-cacheable to avoid this possibility. John -- || John Williams || Brittany, Northern France Who is John Williams? http://www.picindex.info/author/ E-mail replies only accepted from RISC OS machines Somewhere nice to stay in Brittany? http://petit.four.free.fr/visitors/locate
