On Wed, Jul 19, 2006 at 11:35:23AM -0600, Reid Rivenburgh wrote: > On Wed, Jul 19, 2006 at 05:32:19PM +0000, Miciah Dashiel Butler Masters wrote: > > On Fri, Jul 14, 2006 at 01:41:38PM -0600, Reid Rivenburgh wrote: > > > On Fri, Jul 14, 2006 at 06:39:23AM +0000, Miciah Dashiel Butler Masters > > > wrote: > > > > Go to Setup -> Options manager -> Document -> Cache -> Ignore > > > > cache-control info from server and set that option to 0. > > > > > > I forgot about that option. That's already set to 0. > > > > When you say 'already', do you mean that you have the problem even with > > the option disabled? > > Yes, that's what I meant. Sorry about the confusion.
Looking at the document, I don't see any headers to indicate that ELinks should reload it: HTTP/1.1 200 OK Date: Wed, 19 Jul 2006 17:42:19 GMT Server: Apache/1.3.34 (Unix) mod_gzip/1.3.26.1a Vary: Accept-Encoding Last-Modified: Wed, 19 Jul 2006 17:42:01 GMT ETag: "8d4622-c8b2-44be6ee9" Accept-Ranges: bytes Connection: close Content-Type: text/html Content-Encoding: gzip Content-Length: 18374 Do the browsers with which you are familiar actually check every time when you view a document (presumably using the HTTP If-Modified-Since header) whether there is a newer copy on the server? ELinks could do that, but it would be a little complex, and far too slow. I can't even stand the behaviour with ignore_cache_control disabled, which only affects documents that explicitely signal that they should be reloaded from the server. Such behaviour might be acceptable if done in the background, but then it would be a bit confusing (you load the document, you start to read it, then it suddenly updates while you're in the middling of reading it). -- Miciah Masters <[EMAIL PROTECTED]> / <[EMAIL PROTECTED]> _______________________________________________ elinks-users mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-users
