unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: thomas@m3y3r.de, 32658@debbugs.gnu.org
Subject: bug#32658: gnutls + non-blocking url-retrieve
Date: Tue, 24 Sep 2019 07:18:27 +0200	[thread overview]
Message-ID: <87mueu46ho.fsf@gnus.org> (raw)
In-Reply-To: <87mujmee27.fsf@gmail.com> (Noam Postavsky's message of "Thu, 16 May 2019 09:14:56 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

> It sounds like this might be Bug#34341, the problem was
> emacs_gnutls_read didn't handle GNUTLS_E_AGAIN properly.  The symptoms
> only seem to occur with servers supporting TLS1.3 and more recent gnutls
> versions (I thought it was 3.6+, but I haven't pinned the precise
> version numbers, so maybe 3.5.19 has it too, or maybe it's a bit
> different on Windows).  And some people reported that increasing
> gnutls-log-level made it go away, so it's certainly timing dependent.
>
> So can you check if the problem is fixed in the latest emacs-26 or
> master branch?

More information was requested, but no response was given within a few
months, so I'm closing this bug report.  If the problem still exists,
please reopen this bug report.

(And it seems likely that this problem has been fixed.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-09-24  5:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  9:22 bug#32658: 26.1; Cannot connect to TLS websites thomas
2018-09-30 21:33 ` bug#32658: gnutls + non-blocking url-retrieve thomas
2018-10-01  6:03   ` Eli Zaretskii
2018-10-01 20:48     ` thomas
2018-10-05 18:25       ` Noam Postavsky
2018-10-03 14:15     ` thomas
2018-10-07 13:42       ` thomas
2019-05-16 13:14         ` Noam Postavsky
2019-09-24  5:18           ` Lars Ingebrigtsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mueu46ho.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=32658@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=thomas@m3y3r.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).