all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Ruijie Yu <ruijie@netyu.xyz>, emacs-devel@gnu.org
Subject: Re: master 0910230be6e: ; Prefer HTTPS to HTTP in more links
Date: Fri, 4 Aug 2023 09:29:12 +0200	[thread overview]
Message-ID: <CADwFkmm=bnG=cvnSHkQ=4tcijiC2DvCzGfpFjHmCWwbShvb0CQ@mail.gmail.com> (raw)
In-Reply-To: <CAP_d_8UHzrwQGp+kobBrX5b1jPHvxBbmb0tb1GK4j+s7TnMs6g@mail.gmail.com>

> > I believe there are some places where you modified, where http is indeed intended rather than https.  For example, doc/misc/org.org tries to tell readers that Org supports many protocols, one of which is http.

True.  It's not the best example though, as it now redirects to the
https version.

(Are we sure we need an example for HTTP when we already have an HTTPS
one?  HTTPS implies HTTP, doesn't it?)

> An https connection by IP address is unlikely to “work” (though it
> will fail with a different diagnostic). The server will present a TLS
> certificate for a certain domain name, and the client will reject it
> because the domain name presented does not exactly match the IP
> address.
>
> (Also, Gmail’s spell checker says “is now probably now rare” is
> probably a typo.)

That section has been commented out since 2007.  Perhaps it should
simply be removed.



  parent reply	other threads:[~2023-08-04  7:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230802214156.1EF72C038BC@vcs2.savannah.gnu.org>
2023-08-03  5:56 ` master 0910230be6e: ; Prefer HTTPS to HTTP in more links Ruijie Yu via Emacs development discussions.
2023-08-03  6:37   ` Yuri Khan
2023-08-03  6:59     ` Po Lu
2023-08-04  7:48       ` Stefan Kangas
2023-08-03  7:53     ` Michael Albinus
2023-08-04  7:50       ` Andreas Schwab
2023-08-04  7:29     ` Stefan Kangas [this message]
2023-08-04  7:37       ` Eli Zaretskii

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='CADwFkmm=bnG=cvnSHkQ=4tcijiC2DvCzGfpFjHmCWwbShvb0CQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ruijie@netyu.xyz \
    --cc=yuri.v.khan@gmail.com \
    /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.