unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Cooper <cooperc@ocf.berkeley.edu>
To: 36499@debbugs.gnu.org
Subject: bug#36499: 26.2.90; file-error spinner-1.7.3.el, Bad Request
Date: Mon, 22 Jul 2019 19:36:44 -0700	[thread overview]
Message-ID: <CAMjtqDF9RqTm+ma0R8=asdhuhgNm=Wke2oAeLsF6MmT31BcJcQ@mail.gmail.com> (raw)
In-Reply-To: <20190704033917.1D71980059@mailuser.nyi.internal>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

I can reproduce this issue on Arch Linux, Emacs 26.2. To reproduce, I run
emacs -Q and eval the following in *scratch*

(package-initialize)
(package-install 'spinner)

Looks like the actual response says:
> Your browser sent a request that this server could not understand.
> Reason: You're speaking plain HTTP to an SSL-enabled server port.
> Instead use the HTTPS scheme to access this URL, please.

Since this only happens on HTTPS, it's a bit hard to MITM to figre out
what's actually going down. However, Wireshark shows some interesting
stuff: Emacs seems to complete a TLS handshake, then after some packets,
sends a TCP RST. Then, astonishingly, Emacs sends a plaintext HTTP request
_on port 443_ to the server.

I can provide the Wireshark pcap if needed, though I doubt it's too
helpful. Let me know if there's any other way I can help debug.

Thanks,
Christopher Cooper

[-- Attachment #2: Type: text/html, Size: 1206 bytes --]

  parent reply	other threads:[~2019-07-23  2:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  3:39 bug#36499: 26.2.90; file-error spinner-1.7.3.el, Bad Request Brady Trainor
2019-07-08 20:54 ` Lars Ingebrigtsen
2019-07-11  6:35   ` Brady Trainor
2019-07-11 14:01     ` Lars Ingebrigtsen
2019-07-12  3:01       ` Brady Trainor
2019-07-12 14:23         ` Lars Ingebrigtsen
2019-07-12 20:06           ` Brady Trainor
2020-09-05  1:12             ` Stefan Kangas
2020-10-01 12:51               ` Stefan Kangas
2019-07-23  2:36 ` Christopher Cooper [this message]
2019-07-23  3:05   ` Noam Postavsky
2019-07-23  8:19     ` Robert Pluim
2019-07-24 20:35       ` Christopher Cooper

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='CAMjtqDF9RqTm+ma0R8=asdhuhgNm=Wke2oAeLsF6MmT31BcJcQ@mail.gmail.com' \
    --to=cooperc@ocf.berkeley.edu \
    --cc=36499@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).