On Sat, May 20, 2017 at 03:20:21AM +0100, Zefram wrote:
> Package: lynx-cur
> Version: 2.8.9dev1-2+deb8u1
> Severity: important
> 
> Lynx has developed a habit of finding it difficult to load the same web
> page twice in one session, for pages in some websites but not others.

This report doesn't indicate a version where Lynx behaves as you expect.

> Where the bug is in effect, the first loading of any page from an affected
> website works normally, but then any second or subsequent attempt to
> load the same page shortly thereafter fails.  This happens for almost
> any means of invoking a page load: following a link from another page,
> typing in the URL manually, or following a link from the browser's
> "visited links" page.  But page loading succeeds if invoked by following
> a link from the browser's "history" page, by using the "u" command to pop
> the history stack, or by using the ^R command to reload the current page.
> Where page loading fails due to this bug, there is activity in the status
> line that seems to reflect a network request, but then the activity ends
> and the status line returns to normal without changing page, as if the
> request to load the affected page had never been made.

This sounds like the longstanding Lynx behavior: it doesn't automatically
reload a page which has been read and is cached locally.

-- 
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature

Reply via email to