From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zimoun <zimon.toutoune@gmail.com>,
Roland Everaert <r.everaert@protonmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Re : Re: Installed from guix on fedora 33, nyxt display blank buffer instead of opening urls
Date: Sun, 28 Feb 2021 14:56:13 +0100 [thread overview]
Message-ID: <8735xgi9du.fsf@ambrevar.xyz> (raw)
In-Reply-To: <CAJ3okZ3Fhx3GtJ=3xdzWnRj6HaRxZgVKRQHRO44wfQNX8OEqkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
>> Unfortunately, I still face the same problem. The only notable difference, is the fact that nyxt don't trust the certificate from duckduckgo. But, once I add it with the function add-domain-to-certificate-exceptions, the problem with webkitgtk arise.
>
> Do you mean using the command with '--container'?
>
> Maybe 1. you have a problem of config on your side with the
> certificates; from where do they come from? What does ot happens for
> other website than duckduckgo? Then 2. the
> 'add-domain-to-certicate-exceptions' looks like a bug on the Nyxt
> side.
add-domain-to-certificate-exceptions is the Nyxt equivalent of Firefox
"Add exception" or something like that: it ignores bad certificates for
the HTTPS connection to a given host.
This is the expected behaviour I believe.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
prev parent reply other threads:[~2021-02-28 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 20:14 Installed from guix on fedora 33, nyxt display blank buffer instead of opening urls Roland Everaert via
2021-02-24 9:28 ` zimoun
2021-02-28 12:16 ` Re : " Roland Everaert
2021-02-28 13:45 ` zimoun
2021-02-28 13:56 ` Pierre Neidhardt [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735xgi9du.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=r.everaert@protonmail.com \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.