Re: master 0910230be6e: ; Prefer HTTPS to HTTP in more links

[Yuri Khan]

On Thu, 3 Aug 2023 at 12:58, Ruijie Yu via Emacs development
discussions. <emacs-devel@gnu.org> wrote:

> 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.

To expand on that:

> > diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi
> > index e518330c9b0..291d6600af5 100644
> > --- a/doc/misc/tramp.texi
> > +++ b/doc/misc/tramp.texi
> > @@ -375,7 +375,7 @@ From behind a proxy:
> >
> > @example
> > @group
> > -$ git config --global http.proxy http://user:pwd@@proxy.server.com:8080
> > +$ git config --global http.proxy https://user:pwd@@proxy.server.com:8080
> > $ git clone https://git.savannah.gnu.org/r/tramp.git
> > @end group
> > @end example

This looks suspicious, too. A proxy running on port 8080 and referred
to in a git http.proxy config variable is likely to be an http proxy.

> > @@ -1159,7 +1159,7 @@ opened by the URL library.
> > @c linked with the resolver libraries, it will not be able to get to any
> > @c machines off the local network.  This is characterized by being able
> > @c to reach someplace with a raw ip number, but not its hostname
> > -@c (@url{http://129.79.254.191/} works, but
> > +@c (@url{https://129.79.254.191/} works, but
> > @c @url{https://www.cs.indiana.edu/} doesn't).  This used to happen on
> > @c SunOS4 and Ultrix, but is now probably now rare.  If Emacs can't be
> > @c rebuilt linked against the resolver library, it can use the external

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.)