[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Read error at byte ...

From: Ángel González
Subject: Re: [Bug-wget] Read error at byte ...
Date: Wed, 19 Mar 2014 20:18:41 +0100
User-agent: Thunderbird

On 19/03/14 12:52, Tim Ruehsen wrote:
On Tuesday 18 March 2014 20:05:07 Daniel Kahn Gillmor wrote:
On 03/18/2014 05:31 PM, Tim Rühsen wrote:
$ wget -d --ca-certificate=ca-rsa-cert.pem
--private-key=ca-rsa-key-plain.pem https://example.com:8443
2014-03-18 21:48:04 (1.88 GB/s) - Read error at byte 5116 (The TLS
connection was non-properly terminated.).Retrying.

There seems to be a problem in Wget 1.15 (on Debian SID)...
hm, i'll try to take a look at this.
I just took a look at it and it is not a bug, but might need some discussion.

The server does not send a Content-Length header, so the number of expected
bytes is unknown. Wget expects the server to properly close the connection to
expect the transfer being ok.
In our case, the connection shutdown by the server generates an error at the
Wget side. (I guess this is a difference between SSL and plain TCP
Wget assumes the transfer being incomplete and tries it again and again.
Not really a bug, but also not the result a user would expect...
Saying "the server is buggy" doesn't help either.

In order to close a ssl session, the server should send a close_notify message,
which seems to be what the server is not doing (in addition of not providing
the Content-Length).
IIS is a well-known server not doing it: https://bugs.php.net/bug.php?id=23220

reply via email to

[Prev in Thread] Current Thread [Next in Thread]