From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Sourceforge -> https
Date: Mon, 24 May 2021 19:23:58 +0100 [thread overview]
Message-ID: <5c87af7bb0a3c7184141dd9ddf183f1ca9893dd7.camel@ntlworld.com> (raw)
In-Reply-To: <YKvkx+yTRb8qzI9m@fullerene.field.pennock-tech.net>
On Mon, 2021-05-24 at 13:39 -0400, Phil Pennock wrote:
> On 2021-05-24 at 09:20 +0100, Peter Stephenson wrote:
> > > > > Your website is currently hosted at http://zsh.sourceforge.net with PHP 5.4
> > I've pushed the button: when we're quoting Sourceforge URLs then the new one is:
> >
> > https://zsh.sourceforge.io
> >
> > and the message does explicitly say the old one redirects, so there's no
> > rush to fix up.
>
> Alas, SourceForge do not appear to be quite capable of actually pulling
> that off.
>
> The old URL is now returning:
> 503 Service Unavailable
> No server is available to handle this request.
> instead of redirecting.
It's not that simple. I'm getting correct redirections from correct URLs
on the couple of browsers on the systems I've tried. It might still be
a caching problem?
You didn't try https://zsh.sourceforge.net by accident, did you? That's
refusing to redirect, probably deliberately because of the reason Axel gave.
pws
next prev parent reply other threads:[~2021-05-24 18:24 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
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 [this message]
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=5c87af7bb0a3c7184141dd9ddf183f1ca9893dd7.camel@ntlworld.com \
--to=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).