On Mon, 2007-11-12 at 23:14 +0000, John Williams wrote: > I have never imagined it was NetSurf's fault. I tried other browsers as > well! My theory was it was a cache along the way - hence my request for > no-cache tags on the page!
All a no-cache tag would do is prevent systems which should be caching it from caching it. If the page request is being cached then the intervening cache should be issuing an If-Modified-Since header in its request through to our server which would allow it to notice if the page had changed. What happens if you force a reload in whichever browser? > Not a request for a NetSurf bug solution, merely for a NetSurf web page > modification to make my life easier. The correct thing to do is to determine what is preventing your system from behaving properly and fix that, rather than cripple the behaviour of correctly operating systems out there in response to your issue. > But Rob Kendrick says the cache isn't a problem! So where is the problem? That's what we need to determine. Does a commandline request for the page (E.g. using wget or cURL result in a correctly downloaded uncached page? D. -- Daniel Silverstone http://www.digital-scurf.org/ PGP mail accepted and encouraged. Key Id: 2BC8 4016 2068 7895
