[Top][All Lists]

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

[Bug-wget] [bug #45792] wget: Read error in TLS connection with openssl

From: Tim Ruehsen
Subject: [Bug-wget] [bug #45792] wget: Read error in TLS connection with openssl s_server -www server
Date: Fri, 08 Jan 2016 15:55:18 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 Iceweasel/43.0.2

Update of bug #45792 (project wget):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 
         Reproducibility:                    None => Every Time             


Follow-up Comment #1:

Reproducable with (from wget source directory):
$ cd tests/certs
$ openssl s_server -CAfile x509-ca-cert.pem -key x509-server-key.pem -cert
x509-server-cert.pem -www

>From another console:
$ wget --ca-certificate tests/certs/x509-ca-cert.pem -O out.html
Read error at byte 6701 (The TLS connection was non-properly terminated.)

BTW, out.html is complete

Looking at the debug output reveals that the server response does not send a
Content-Length header line. So the client does not know that the data is
complete and leaves the connection open, waiting for more data to come or for
the server to close the connection. Here we see the server closing the
connection improperly which is interpreted as an error by Wget. And thus the

Curl has the same problem, saying "The TLS connection was non-properly
terminated" and returning with $? 56. Regarding the curl man page this is
"Failure in receiving network data.".

This bug either has to be fixed in 'openssl s_server' (or in GnuTLS if and
only if this is a misinterpretation of TLS standards by GnuTLS).


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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