Your message dated Wed, 05 Jul 2017 13:49:16 +0000
with message-id <[email protected]>
and subject line Bug#863008: fixed in lynx 2.8.9dev15-1
has caused the Debian Bug report #863008,
regarding failing to load previously-loaded pages of some websites
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
863008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863008
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
The envelope of this bug is a bit tricky.

As far as I can see, within any particular Lynx session this bug affects
a fixed set of websites: a site that is affected is affected for the
whole session, and a site that does not exhibit the problem won't come
to exhibit it later in the session.  A "website" for this purpose is
the combination of scheme prefix and authority part of a URL.  All paths
within a website are affected together.  I have not been able to determine
whether different scheme/authority combinations that involve the same
hostname can be affected distinct from each other, but ones involving
different hostnames are definitely distinct.  The websites that I have
found affected so far are only HTTPS ones.

Which websites are affected is mostly consistent between Lynx sessions.
For the past few weeks I have found that <https://en.wikipedia.org> is
affected in all my Lynx sessions.  Recently <https://www.theguardian.com>
has come to be affected in most sessions, but not entirely consistently.
Most websites remain unaffected.  I have no idea what distinguishes the
affected websites from unaffected ones.

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.

The inability to load a page twice applies separately to each page in the
affected website.  Loading a different page (with different URL) works.
Many pages from the same website may be loaded in sequence.  But then
attempting to load the same pages again fails: each previously-loaded
page cannot be loaded again.  Such failing page loads can be arbitrarily
interleaved with successful first-time page loads.

However, an attempted repeated page load may succeed if enough activity
has taken place since the first (successful) load of that page.  "Enough
activity" seems to be constituted by successful loads of sufficiently
many other pages.  (Perhaps a caching issue?)  Repeatedly attempting to
load a failing page, with no other activity between attempts, doesn't
make it succeed.  After a successful repeated page load, further attempts
to load the same page again go back to failing.

-zefram

--- End Message ---
--- Begin Message ---
Source: lynx
Source-Version: 2.8.9dev15-1

We believe that the bug you reported is fixed in the latest version of
lynx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert <[email protected]> (supplier of updated lynx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 05 Jul 2017 15:18:34 +0200
Source: lynx
Binary: lynx-common lynx lynx-cur
Architecture: source all amd64
Version: 2.8.9dev15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lynx Packaging Team <[email protected]>
Changed-By: Axel Beckert <[email protected]>
Description:
 lynx       - classic non-graphical (text-mode) web browser
 lynx-common - shared files for lynx package
 lynx-cur   - Text-mode WWW Browser (transitional package)
Closes: 408448 863008
Changes:
 lynx (2.8.9dev15-1) unstable; urgency=medium
 .
   * Import upstream version 2.8.9dev15
     + Refresh patches where necessary.
     + Adds a note in lynx.cfg about default values. (Closes: #408448)
     + Correct logic in HTCopy() when re-reading a page. (Closes: #863008)
   * debian/copyright: Change some URLs to HTTPS as suggested by DUCK.
   * Remove lintian override for "iff" false positive again, as #865055 is
     now fixed in lintian.
Checksums-Sha1:
 912618d203aa6761d45abdb0f7df3ee8ce20bdd2 2328 lynx_2.8.9dev15-1.dsc
 faa5c880345fe0e0df872a7add53ad80c518f90e 2671180 lynx_2.8.9dev15.orig.tar.bz2
 534004dae3b454be14d988261deaf9c48208741c 27604 lynx_2.8.9dev15-1.debian.tar.xz
 00d6957b4f8b11b28f67813242f3accb3ad8f488 1102958 
lynx-common_2.8.9dev15-1_all.deb
 3fbe22535f1039a43e84b509144be43461184384 241510 lynx-cur_2.8.9dev15-1_all.deb
 b457ca7ef63189afe786b63b6c88c159474909e2 1545268 
lynx-dbgsym_2.8.9dev15-1_amd64.deb
 b6702132fc92874e1251112d9a6524a812027c1e 7400 lynx_2.8.9dev15-1_amd64.buildinfo
 282730c98569c376a4fb409ceb9dc530ac376135 632192 lynx_2.8.9dev15-1_amd64.deb
Checksums-Sha256:
 1a3a7d71764ece212f91fec6e1dbcc4b18a9e16b6b54e69318f5c5fbf873cc67 2328 
lynx_2.8.9dev15-1.dsc
 4810719102b33b21aa3c360e1b33a94696dba5ed5aa37e8fd1178c10d5c96d99 2671180 
lynx_2.8.9dev15.orig.tar.bz2
 aa8d8cf86c124696fefa2cea070e99cdecf6c2e1fb68418c337bf41bddef1c2e 27604 
lynx_2.8.9dev15-1.debian.tar.xz
 f5d8ccf0882e4d39825ee135d13f7653ba3594e31ce606ff359d92928796a781 1102958 
lynx-common_2.8.9dev15-1_all.deb
 ded7d2d360764d2680f290cebc024f0f9479484bdfbee2d2890e7b0df5325fe3 241510 
lynx-cur_2.8.9dev15-1_all.deb
 fe19b18b5e525303c707fbf064bf6974acdb801ed260d35ef58ffcdda752ec9f 1545268 
lynx-dbgsym_2.8.9dev15-1_amd64.deb
 b0aacbbdd2d4b08628d392611e3a502f976112e72601fbd664fd8ef1212615b8 7400 
lynx_2.8.9dev15-1_amd64.buildinfo
 36eb7cbce86d8e228c2aad9ca7652c68501f47f295de637597e54665d2d03069 632192 
lynx_2.8.9dev15-1_amd64.deb
Files:
 a17dd216afa32ad846c5e15131d1f672 2328 web optional lynx_2.8.9dev15-1.dsc
 eff9092d2436dc2e6ab4bddf332c9e89 2671180 web optional 
lynx_2.8.9dev15.orig.tar.bz2
 59d3aa060a4c04943543823e070ffa5d 27604 web optional 
lynx_2.8.9dev15-1.debian.tar.xz
 8cb7ada0dc12871f7dcdcce325d1ac8a 1102958 web optional 
lynx-common_2.8.9dev15-1_all.deb
 fb3e1c99b476bc90930d881e2e22c7bc 241510 oldlibs extra 
lynx-cur_2.8.9dev15-1_all.deb
 cbf99c3ec13e7312c7819ec116c8724d 1545268 debug extra 
lynx-dbgsym_2.8.9dev15-1_amd64.deb
 a90614a741ff7ab66c47224ddb2de5d4 7400 web optional 
lynx_2.8.9dev15-1_amd64.buildinfo
 5c4862124441789afe4cf2d3e2d6e872 632192 web optional 
lynx_2.8.9dev15-1_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAllc6C0ACgkQa+Zjx1o1
yXWMtA//eL+qJU/r/vIUhq6o6Ev6hWsTMgFaHclCpF2UMFMP0ofYLdMhTkSer51y
uW2+A7HvdGgJV7yc1/e+X5VWG03xR+HNntpXhDj8yf7IG82aN20TFKtpgrpoSrMl
RGuaChOdwGM+Hs75T83KQrYAyYbz7R4AVZhH+5+SqilImH0G+f2NITSrPgl+Nm4g
Hlt/nQiNkr8kszN9Qosv7WxfIgY2zSdku+eT05prItK2Ynnu9Lq5lWb0qeyCGppA
eNGB3MDF+ER26pEIbUuYKhZ5BSgNKBUVY+PD3aCrZyjbw3oxv3KlEw5fsm4xH/Q/
1RKBGx8TA5NrxHUSdQXcifLjU3HKlw6hR3rJGurWMV2I8Uhy7/dQJIpGXmSpVaRb
kJ2MbFMu8LuMxfMexuqNPcn2jXA6QZwnn1N1KXty5cBcUyN++8qNG8A6s1q/uC/3
mKyavdn7QVB86OtJoE9XyDDqT97wyE7OHtp5yfjI2mx2PCmHIIF7oPn4RBbudEo0
JXt1AHHDj/xPIGbSKBtMAq2Dbf1M9W5wObVIqya2VzE6iCEY9O8b4ra4s+YcqPj7
wY5gs10mHF+8NN2c0IH0XpUoeG4nah7MZOF+ZzFt/v3q0yihCsEBGQ96TNWEszRs
vO0bgcpjTHF0edETvsl8fQl/CfVAckeqZfI6jTsR91tjR5/NmJ4=
=chIP
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to