unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Nicolas Graner <nicolas@graner.name>
To: help-gnu-emacs@gnu.org
Subject: url-retrieve fails on most HTTPS sites
Date: Mon, 28 Sep 2020 22:41:02 +0200	[thread overview]
Message-ID: <87sgb1my75.fsf@hypra-graner> (raw)

Hello all,

using 26.1 on Debian, I try to open various web pages with url-retrieve.
It works with all HTTP and some HTTPS connections, but fails with most
HTTPS. For instance with Wikipedia:

  (switch-to-buffer (url-retrieve "https://wikipedia.org/" '(lambda (&rest ignore))))

The buffer that shows up is empty. Tracing url-http-async-sentinel gives:

======================================================================
1 -> (url-http-async-sentinel #<process wikipedia.org> "open
")
1 <- url-http-async-sentinel: nil
======================================================================
1 -> (url-http-async-sentinel #<process wikipedia.org> "connection broken by remote peer
")
1 <- url-http-async-sentinel: nil

In contrast, The Conversation is OK:
  (switch-to-buffer (url-retrieve "https://theconversation.com/fr/" '(lambda (&rest ignore))))
works fine, the buffer contains HTTP headers followed by à HTML page.

I don't use a proxy. The result is the same whether url-privacy-level
is 'none or 'paranoid.

Any suggestions as to what could make some sites close the connection,
or how I could find out more?

Thanx for your help.
Nicolas



             reply	other threads:[~2020-09-28 20:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 20:41 Nicolas Graner [this message]
2020-09-28 23:13 ` url-retrieve fails on most HTTPS sites Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-28 23:24   ` 2QdxY4RzWzUUiLuE
2020-09-28 23:41     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29  2:26       ` Stefan Monnier
2020-09-29  3:24         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29  9:31           ` tomas
2020-09-29  9:49             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 10:32               ` tomas
2020-09-29 10:50                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 14:14                   ` Sharp--quote [was: url-retrieve fails on most HTTPS sites] tomas
2020-09-29 14:56                     ` Stefan Monnier
2020-09-29 15:19                       ` tomas
2020-09-29 16:03                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 16:01                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 15:18                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29  3:45         ` url-retrieve fails on most HTTPS sites 황병희
2020-09-29  2:50       ` 2QdxY4RzWzUUiLuE
2020-09-29  5:45         ` Colin Baxter
2020-09-29 11:29           ` 2QdxY4RzWzUUiLuE
2020-09-29 13:57             ` Colin Baxter
2020-09-29 14:53         ` HTTPS fails (was: url-retrieve fails on most HTTPS sites) Nicolas Graner
2020-09-29 15:10           ` Nicolas Graner
2020-09-29 15:16           ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-29 14:47 ` url-retrieve fails on most HTTPS sites Noam Postavsky
2020-09-29 15:08   ` Nicolas Graner

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=87sgb1my75.fsf@hypra-graner \
    --to=nicolas@graner.name \
    --cc=help-gnu-emacs@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.
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).