That is also possible. Would have to check again. And this is why I prefer
to work from distributions rather than "latest". To many variables that may
adversely a package meant to have minimal dependancies.
However, thanks again for the reminder.
On Wed, Jun 29, 2016 at 3:56 PM, Tim Ruehsen wrot
Hello,
gnutls_handshake() is documented to possibly return GNUTLS_E_INTERRUPTED as
well as GNUTLS_E_AGAIN and should probably behave similarly for both return
codes within wget.
diff --git a/src/gnutls.c b/src/gnutls.c
index 63c7c33..44c497b 100644
--- a/src/gnutls.c
+++ b/src/gnutls.c
@@ -46
Thanks, Jérémie.
The change has been pushed.
Tim
signature.asc
Description: This is a digitally signed message part.
Thanks, Daniel.
I believe, we already handle that case.
If GNUTLS_E_INTERRUPTED occurs, we restart the loop and re-enter
gnutls_handshake(). This happens for all non-fatal errors.
That is the while part
while (err && gnutls_error_is_fatal (err) == 0);
Tim
On Thursday 30 June 2016 15:18
On Thu, 30 Jun 2016, Tim Ruehsen wrote:
I believe, we already handle that case. If GNUTLS_E_INTERRUPTED occurs, we
restart the loop and re-enter gnutls_handshake(). This happens for all
non-fatal errors.
Right, but then it won't wait for the socket and just busy-loop. The
gnutls_record_get_d