unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 16253@debbugs.gnu.org
Subject: bug#16253: 24.3.50; Irrelevant warnings from gnutls
Date: Mon, 20 Jan 2014 12:19:52 -0800	[thread overview]
Message-ID: <87r4829ziv.fsf@building.gnus.org> (raw)
In-Reply-To: <87mwiqpr9q.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Mon, 20 Jan 2014 11:11:29 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> The URL library can't trap these.  GnuTLS considers them highest
> priority, so blocking them out would block most useful log information.

Useful to whom?  It's probably useful when developing applications that
talk TLS, but it's not useful to the user who's just trying to read a
web page.

If you're reading a page, and you're loading a picture that fails, Emacs
should display a "failed download" image, not spew TLS-level errors to
the user.  The user isn't interested.

So I think that, basically, no TLS errors should be displayed to the
user.  At least I haven't seen one yet that's been useful to me as a
user.

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





  reply	other threads:[~2014-01-20 20:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-25  9:09 bug#16253: 24.3.50; Irrelevant warnings from gnutls Lars Ingebrigtsen
2014-01-07 23:47 ` Ted Zlatanov
2014-01-18 17:29   ` Lars Ingebrigtsen
2014-01-18 17:57     ` Eli Zaretskii
2014-01-20 16:11       ` Ted Zlatanov
2014-01-18 18:06     ` Lars Ingebrigtsen
2014-01-20 16:11       ` Ted Zlatanov
2014-01-20 20:19         ` Lars Ingebrigtsen [this message]
2014-02-10  2:34           ` Ted Zlatanov
2014-02-10  3:01             ` Lars Ingebrigtsen
2014-02-10 10:42               ` Ted Zlatanov
2014-12-08 19:58 ` Lars Magne Ingebrigtsen

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=87r4829ziv.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=16253@debbugs.gnu.org \
    /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).