unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: 29258-done@debbugs.gnu.org
Subject: bug#29258: web client fails on https
Date: Wed, 22 Nov 2017 17:50:23 +0100	[thread overview]
Message-ID: <87d14aw94g.fsf@gnu.org> (raw)
In-Reply-To: <9fb4c0b8449d55cf3507789191631eb6@hypermove.net> (Amirouche Boubekki's message of "Wed, 22 Nov 2017 17:03:43 +0100")

Amirouche Boubekki <amirouche@hypermove.net> skribis:

> On 2017-11-22 16:21, ludo@gnu.org wrote:
>> Hi Amirouche,
>>
>> Amirouche Boubekki <amirouche@hypermove.net> skribis:
>>
>>> GNU Guile 2.2.2
>>> Copyright (C) 1995-2017 Free Software Foundation, Inc.
>>>
>>> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
>>> This program is free software, and you are welcome to redistribute it
>>> under certain conditions; type `,show c' for details.
>>>
>>> Enter `,help' for help.
>>> scheme@(guile-user)> (use-modules (web client))
>>> scheme@(guile-user)> (http-get "https://www.gnu.org")
>>> ERROR: In procedure get-bytevector-n:
>>> ERROR: Throw to key `gnutls-error' with args `(#<gnutls-error-enum La
>>> connexion TLS n’a pas été terminée correctement.>
>>> read_from_session_record_port)'.
>>
>> I cannot reproduce this in current ‘stable-2.2’.  I believe this was
>> fixed by commit 0c102b56e98da39b5a3213bdc567a31ad8ef3e73.
>>
>> Can you confirm that ‘stable-2.2’ works for you?
>>
>
> Yes.

Thanks,
Ludo'.





      reply	other threads:[~2017-11-22 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 14:09 bug#29258: web client fails on https Amirouche Boubekki
2017-11-22  6:28 ` Christopher Allan Webber
2017-11-22 15:21 ` Ludovic Courtès
2017-11-22 16:03   ` Amirouche Boubekki
2017-11-22 16:50     ` Ludovic Courtès [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/guile/

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

  git send-email \
    --in-reply-to=87d14aw94g.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=29258-done@debbugs.gnu.org \
    --cc=amirouche@hypermove.net \
    /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.
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).