From: Hideki Saito <hidekis@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: EWW problems with SNI https sites?
Date: Thu, 11 Jul 2019 01:50:57 -0700 [thread overview]
Message-ID: <CAAaRP5uZH5O4XxBQoMfr2Htqx0ak1T55=J80w7_BjsjhFTwh1g@mail.gmail.com> (raw)
Hello,
I'm having a bit of problem with EWW accessing some sites under Windows,
namely, some sites returning "400 Bad Request" -- the reason being "The
plain HTTP request was sent to HTTPS port"
This seems to affect a lot of CloudFlare hosted sites. But even without
CloudFlare, this seems to be affecting SNI (Server Name Indication -- ones
without dedicated IP address) hosts as well.
Here's the pattern I'm seeing:
1) https://www.hidekisaito.com (CloudFlare) -- doesn't work
2) https://hidekisaito.com (SNI) -- doesn't work
3) https://duckduckgo.com -- works
4) https://twitter.com -- works
5) https://helpa.hidekisaito.com (SNI) -- doesn't work (due to the
maintenance, the site might be down for next few hours.
I have my personal ELPA site on #5 site, and this seems to be causing
issue; M-x list-package fails with the same error, M-x
package-refresh-content somehow successfully fetch the list. (But doesn't
help as fetching and installing the package would fail with 400 Bad Request)
I can live with eww not working, but it's painful that list-package doesn't
work. Do you happen to know if there are anyways to force list-package (and
package download) to use the method used by package-refresh-content?
Please let me know if this is something I should be reporting as a bug.
Thank you.
Hideki Saito (斉藤英樹)
next reply other threads:[~2019-07-11 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 8:50 Hideki Saito [this message]
2019-07-11 9:31 ` EWW problems with SNI https sites? Colin Baxter
2019-07-11 12:53 ` Eli Zaretskii
[not found] ` <mailman.898.1562835105.2688.help-gnu-emacs@gnu.org>
2019-07-11 13:28 ` Lars Magne Ingebrigtsen
2019-07-13 5:03 ` Hideki Saito
2019-07-14 5:24 ` Hideki Saito
2019-07-15 10:28 ` Robert Pluim
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='CAAaRP5uZH5O4XxBQoMfr2Htqx0ak1T55=J80w7_BjsjhFTwh1g@mail.gmail.com' \
--to=hidekis@gmail.com \
--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.
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.