From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: Sourceforge -> https
Date: Fri, 21 May 2021 17:40:19 +0200 [thread overview]
Message-ID: <CAHYJk3RDmTpaQY_Fg9WeKgFY0eG24KaSdAqvCaZFzLcg3VpNfQ@mail.gmail.com> (raw)
In-Reply-To: <1403418415.301394.1621610617915@mail2.virginmedia.com>
On 5/21/21, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> I just logged into Sourceforge for the first time for ages and realised
> I never did anything about switching from http-based to https-based web
> pages which I was prompted about years ago. That seems pretty
> uncontroversial nowadays --- everybody and their dog are redirecting you
> to https. Any good reason not to switch?
>
> The prompt is as follows.
>
> Your website is currently hosted at http://zsh.sourceforge.net with PHP 5.4
>
> To update to https://zsh.sourceforge.io and PHP 7.x, click the button
> below.
> There will be a small delay for it to take effect. You may switch back if
> needed.
The tld being different seems a bit more concerning than the change to
https, but presumably the old urls will continue to redirect?
--
Mikael Magnusson
next prev parent reply other threads:[~2021-05-21 15:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 15:23 Peter Stephenson
2021-05-21 15:40 ` Mikael Magnusson [this message]
2021-05-21 15:47 ` Peter Stephenson
2021-05-21 15:53 ` Axel Beckert
2021-05-24 8:20 ` Peter Stephenson
2021-05-24 12:09 ` Peter Stephenson
2021-05-24 18:26 ` Daniel Shahaf
2021-05-24 17:39 ` Phil Pennock
2021-05-24 18:18 ` Bart Schaefer
2021-05-24 18:23 ` Peter Stephenson
2021-05-24 18:57 ` Phil Pennock
2021-05-24 19:43 ` website links (Re: Sourceforge -> https) Phil Pennock
2021-05-24 20:06 ` Bart Schaefer
2021-05-24 20:16 ` Phil Pennock
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=CAHYJk3RDmTpaQY_Fg9WeKgFY0eG24KaSdAqvCaZFzLcg3VpNfQ@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).