all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: gnu@crabapple.me.uk
Cc: 36810@debbugs.gnu.org
Subject: bug#36810: 26.2; package.el; package-refresh-contents, Bad Request (http over https)
Date: Thu, 25 Jul 2019 13:35:25 -0400	[thread overview]
Message-ID: <85ef2ej9uq.fsf@gmail.com> (raw)
In-Reply-To: <2e1fffbb-6826-628a-e598-fcdb3ce9d89b@crabapple.me.uk> (gnu@crabapple.me.uk's message of "Thu, 25 Jul 2019 17:42:57 +0100")

merge 36810 36725
quit

gnu@crabapple.me.uk writes:

> Replicate with:
> emacs -Q
> M-x package-initialize RET
> M-x set-variable RET debug-on-error RET t RET
> package-refresh-contents
> => Debugger entered--Lisp error: (file-error
> "https://elpa.gnu.org/packages/archive-contents" "Bad Request")
>
> In wireshark I observe a TLS1.2 session with elpa.gnu.org, terminated
> from localhost, then another connection established to port 443 on
> elpa.gun.org but no TLS setup and then a straight HTTP GET request (for
> /packages/archive-contents).
> Server responds 400 (Bad Request):
> "Your browser sent a request that this server could not understand.
> Reason: You're speaking plain HTTP to an SSL-enabled server port."

I believe this is another case of Bug#36725/36749/34341.  It should work
in 26.2.90 pretest.  As a workaround, doing

    (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")

seems to help (it somehow affects the timing so as to avoid the bug).





  parent reply	other threads:[~2019-07-25 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 16:42 bug#36810: 26.2; package.el; package-refresh-contents, Bad Request (http over https) gnu
2019-07-25 17:30 ` Eli Zaretskii
2019-07-25 17:35 ` Noam Postavsky [this message]
2019-07-25 21:20   ` gnu

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=85ef2ej9uq.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=36810@debbugs.gnu.org \
    --cc=gnu@crabapple.me.uk \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.