Re: [Lynx-dev] Problems accessing wikipedia with lynx 2.8.8

[X dej]

Is this problem related (but not quite similar) to the failure to send non
trivial attachments (80kBytes or more) or long mails (15kBytes) with lynx to
gmail and to Zimbra's webmails ?

This has been the case for at least 6 years, and still is a problem
happening today.

Below I forward a private mail discussing the matter.

Sincerely yours,

anonymous lynx lover.

---------- Forwarded message ----------
From: dREPLACEeLETTEReEjBYeLETTEReAatGMA ILcom
<address@hidden>
Date: Sun, 11 May 2014 11:27:03 +0200
Subject: Re: [Lynx-dev] Lynx on Gmail and on my webmail
To: Thomas Dickey <address@hidden>

http://lists.gnu.org/archive/html/lynx-dev/2014-05/msg00008.html

2014-05-10 13:15 UTC+02:00, Thomas Dickey <address@hidden>:
> On Fri, May 09, 2014 at 07:21:25PM +0000, address@hidden wrote:
>> > From: dREPLACEeLETTEReEjBYeLETTEReAatGMA ILcom
>> >    <address@hidden>
>> ....................
>> >
>> > There seems to be a problem with submission of long text in forms to
>> > https.
>> >
>> > I use Lynx 2.8.8dev.15 (18 Nov 2012) on Gmail (
>> > https://mail.google.com/mail/h/16gqxd6fxycvr/?&v=b&pv=tl&cs=b )
>> >
>> > When sending a big email, the https submission stalls then fails. This
>> > is
>> > reproductible, use a mail text of 200 lines and 15kBytes.
>> >
>> > Am I alone to have that problem ?
>>
>> No, I've definitly encountered it.
>> Fortunately for me, it has been in forwarding email,
>> and almost always, I can trim almost all of the forwarding
>> to just enough to indicate a mailing that the people are
>> top posting in response to, for some context.   :-)

I realized the same thing one week ago. And I decided to bugreport about it.

But now I think the same bug prevents me from sending attachments, so this is
actually problematic to me.

Here are the relevant statusline messages:

40. Alert!: Unable to access document.
39. Can't Access
`https://mail.google.com/mail/u/0/h/1p9asKfr3Ghxn/?&v=b&fv=b&cpt=c&at=AF6VLQ&pv=cv&cs=c&th=145eee'
38. Alert!: Unexpected network read error; connection aborted. [showed
up after a long blocking moment]
37. HTTP request sent; waiting for response.
36. Sending HTTP request.
35. Secure 128-bit TLS1.1 (RSA_AES_128_CBC_SHA1) HTTP connection
34. Certificate issued by: /C=US/O=Google Inc/CN=Google Internet Authority G2
33. Verified connection to mail.google.com (cert=mail.google.com)
32. Making HTTPS connection to mail.google.com
31. Looking up mail.google.com

> so... is it a new bug (a regression), or something that we've stumbled onto
> after a while?

I thought gmail and my boss's webmail made impossible to me to send
attachments. But I just thinked again about that: I just successfully
sent my first attachment with lynx on a webmail on https, an
attachment of 8885 bytes.

So I think this bug is here since at least three or four years, when
gmail started to use https.

Sorry for the subject line of this thread, broken at "From:".

2017-10-27 14:54 UTC+02:00, Thomas Dickey <address@hidden>:
> ----- Original Message -----
> | From: "Dick Wesseling" <address@hidden>
> | To: address@hidden
> | Sent: Thursday, October 26, 2017 9:14:01 PM
> | Subject: Re: [Lynx-dev] Problems accessing wikipedia with lynx 2.8.8
> |
> |
> | address@hidden wrote:
> |
> | > About two weeks ago, lynx 2.8.8 rel 2, running on this Solaris
> | > system,
> | > ceased to be able to access wikipedia, although it had successfully
> | > done
> | > so for many years.
> | >
> | > Is this a known problem?  Any suggestions appreciated.
> |
> | This is a known problem, known to me at least. Wikipedia used to
> | trigger
> | a bug in Lynx, then they apparently changed something which made Lynx
> | work again, but recently it stopped working again.
> |
> | The bug is that if a server sends a large amount of HTTP headers then
> | Lynx does not read all of the data sent by the server and you get a
> | truncated .gz file.
>
>
> |
> | The reason is as follows:
> |
> | - Network data is delivered to Lynx in chunks.
> |
> | - HTLoadHTTP() reads the first chunk and processes the data in that
> |   chunk, in particular the HTTP response line and the Content-Length
> |   header.
> |   At this moment the input stream can be positioned anywhere!
> |
> | - Next HTLoadHTTP() calls HTCopy() to read and process the bulk
> |   of the data. HTCopy() thinks it can limit the amount read to
> |   anchor->content_length, but that is not true because the stream
> |   is not positioned at the start of the content.
> |
> |   However, HTCopy() usually gets away with this because it always
> |   reads in portions of INPUT_BUFFER_SIZE. This mitigates the problem,
> |   but not enough for Wikipedia.
> |
> | The following patch solves the problem with Wikipedia, but it
> | probably
> | breaks other things.
> |
> | --- lynx2.8.9dev.16/WWW/Library/Implementation/HTFormat.c.bak       Sun Jul
> |  2 19:09:45 2017
> | +++ lynx2.8.9dev.16/WWW/Library/Implementation/HTFormat.c   Fri Oct 27
> | 02:26:46 2017
>
> sounds like this:
>
> https://github.com/ThomasDickey/lynx-snapshots/commit/6d7cd77ddec64888f258f03f5b9efc9d57b09a0c#diff-1371112641c8cfcf23d0c819cb7959cc
>
> http://lynx.invisible-island.net/current/CHANGES.html#v2.8.9dev.15
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863008
>
> --
> Thomas E. Dickey <address@hidden>
> http://invisible-island.net
> ftp://invisible-island.net
>
> _______________________________________________
> Lynx-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lynx-dev
>