* Sourceforge -> https @ 2021-05-21 15:23 Peter Stephenson 2021-05-21 15:40 ` Mikael Magnusson 0 siblings, 1 reply; 14+ messages in thread From: Peter Stephenson @ 2021-05-21 15:23 UTC (permalink / raw) To: zsh workers 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. pws ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-21 15:23 Sourceforge -> https Peter Stephenson @ 2021-05-21 15:40 ` Mikael Magnusson 2021-05-21 15:47 ` Peter Stephenson 2021-05-21 15:53 ` Axel Beckert 0 siblings, 2 replies; 14+ messages in thread From: Mikael Magnusson @ 2021-05-21 15:40 UTC (permalink / raw) To: Peter Stephenson; +Cc: zsh workers 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-21 15:40 ` Mikael Magnusson @ 2021-05-21 15:47 ` Peter Stephenson 2021-05-21 15:53 ` Axel Beckert 1 sibling, 0 replies; 14+ messages in thread From: Peter Stephenson @ 2021-05-21 15:47 UTC (permalink / raw) To: Mikael Magnusson; +Cc: zsh workers > On 21 May 2021 at 16:40 Mikael Magnusson <mikachu@gmail.com> wrote: > 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? I'm pretty sure, yes, otherwise the way of getting in at the moment would have disappeared into history. I think it's just the primary URL that changes. We do have the option of going back. pws ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 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 1 sibling, 1 reply; 14+ messages in thread From: Axel Beckert @ 2021-05-21 15:53 UTC (permalink / raw) To: zsh-workers Hi, On Fri, May 21, 2021 at 05:40:19PM +0200, Mikael Magnusson wrote: > > 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. +1 for moving away from PHP 5.4 (long time EoL already). Do we use PHP at all? HTTPS is fine, too. :-) > The tld being different seems a bit more concerning Well, if I were SF, I would be concerned if I wouldn't do it. Reason for the different TLD is that otherwise every project page could extract valid https://sourceforge.net/ authentication cookies and afterwards impersonate that user. This is one of the reasons why using just the domain itself as website should not be done unless all subdomains are trusted. (Which obviously isn't the case for a hosting business.) Same reason why GitHub pages are hosted under github.io and not github.com. Actually, it is already a concern for old project sites, but since most HTTPS cookies are not sent over plain HTTP, too, it's ok-ish. The cleaner solution for SF would be to use "www.sourceforge.net" and restrict cookies to this hostname instead of the whole domain. (You don't seem to be able to restrict cookies to a domain, but then exclude its subdomains.) But since websites without "www." are totally in fashion these days... (I should shut up here as I have at least one domain I use that way, too. But without using any authentication cookies. :-) > but presumably the old urls will continue to redirect? I think so, yes. At least it works for other projects like e.g. http://octave.sourceforge.net/ → https://octave.sourceforge.io/ HTH Kind regards, Axel -- PGP: 2FF9CD59612616B5 /~\ Plain Text Ribbon Campaign, http://arc.pasp.de/ Mail: abe@deuxchevaux.org \ / Say No to HTML in E-Mail and Usenet Mail+Jabber: abe@noone.org X https://axel.beckert.ch/ / \ I love long mails: https://email.is-not-s.ms/ ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-21 15:53 ` Axel Beckert @ 2021-05-24 8:20 ` Peter Stephenson 2021-05-24 12:09 ` Peter Stephenson 2021-05-24 17:39 ` Phil Pennock 0 siblings, 2 replies; 14+ messages in thread From: Peter Stephenson @ 2021-05-24 8:20 UTC (permalink / raw) To: zsh-workers > On 21 May 2021 at 16:53 Axel Beckert <abe@deuxchevaux.org> wrote: > On Fri, May 21, 2021 at 05:40:19PM +0200, Mikael Magnusson wrote: > > > 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. > > +1 for moving away from PHP 5.4 (long time EoL already). Do we use PHP > at all? HTTPS is fine, too. :-) > > > The tld being different seems a bit more concerning > > Well, if I were SF, I would be concerned if I wouldn't do it. Thanks for that, that was useful. 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. When this is working I'll try and remember to update the docs in the distribution. pws ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 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 1 sibling, 1 reply; 14+ messages in thread From: Peter Stephenson @ 2021-05-24 12:09 UTC (permalink / raw) To: zsh-workers > On 24 May 2021 at 09:20 Peter Stephenson <p.w.stephenson@ntlworld.com> wrote: > I've pushed the button: when we're quoting Sourceforge URLs then the new one is: > > https://zsh.sourceforge.io It's now live. Here are all the references I can see in the source distribution. pws diff --git a/Doc/Zsh/manual.yo b/Doc/Zsh/manual.yo index 119849e4c..51601adbd 100644 --- a/Doc/Zsh/manual.yo +++ b/Doc/Zsh/manual.yo @@ -196,7 +196,7 @@ produce a nicely formatted printed manual. item(The HTML manual)( An HTML version of this manual is available at the Zsh web site via: -uref(http://zsh.sourceforge.net/Doc/). +uref(https://zsh.sourceforge.io/Doc/). (The HTML version is produced with bf(texi2html), which may be obtained from uref(http://www.nongnu.org/texi2html/). The command is diff --git a/Doc/Zsh/metafaq.yo b/Doc/Zsh/metafaq.yo index 4cefa4d71..c780808e3 100644 --- a/Doc/Zsh/metafaq.yo +++ b/Doc/Zsh/metafaq.yo @@ -29,7 +29,7 @@ uref(https://www.zsh.org/pub/)) The up-to-date source code is available via Git from Sourceforge. See uref(https://sourceforge.net/projects/zsh/) for details. A summary of instructions for the archive can be found at -uref(http://zsh.sourceforge.net/). +uref(https://zsh.sourceforge.io/). texinode(Mailing Lists)(The Zsh FAQ)(Availability)(Introduction) sect(Mailing Lists) @@ -98,6 +98,6 @@ A userguide is currently in preparation. It is intended to complement the manual, with explanations and hints on issues where the manual can be cabbalistic, hierographic, or downright mystifying (for example, the word `hierographic' does not exist). It can be viewed in its current state at -uref(http://zsh.sourceforge.net/Guide/). At the time of writing, chapters +uref(https://zsh.sourceforge.io/Guide/). At the time of writing, chapters dealing with startup files and their contents and the new completion system were essentially complete. diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo index 9f0d99d45..20f6449f1 100644 --- a/Etc/FAQ.yo +++ b/Etc/FAQ.yo @@ -171,20 +171,20 @@ sect(Sources of information) label(11) Information on zsh is available via the World Wide Web. The URL - is url(http://zsh.sourceforge.net/)(http://zsh.sourceforge.net/) . + is url(https://zsh.sourceforge.io/)(https://zsh.sourceforge.io/) . The server provides this FAQ and much else and is now maintained by the zsh workers (email email(zsh-workers@zsh.org)). The FAQ is at \ -url(http://zsh.sourceforge.net/FAQ/)(http://zsh.sourceforge.net/FAQ/) . +url(https://zsh.sourceforge.io/FAQ/)(https://zsh.sourceforge.io/FAQ/) . The site also contains some contributed zsh scripts and functions; we are delighted to add more, or simply links to your own collection. This document was originally written in YODL, allowing it to be converted easily into various other formats. The master source file lives at - url(http://zsh.sourceforge.net/FAQ/zshfaq.yo) -(http://zsh.sourceforge.net/FAQ/zshfaq.yo) and the plain text version - can be found at url(http://zsh.sourceforge.net/FAQ/zshfaq.txt) -(http://zsh.sourceforge.net/FAQ/zshfaq.txt) . + url(https://zsh.sourceforge.io/FAQ/zshfaq.yo) +(https://zsh.sourceforge.io/FAQ/zshfaq.yo) and the plain text version + can be found at url(https://zsh.sourceforge.io/FAQ/zshfaq.txt) +(https://zsh.sourceforge.io/FAQ/zshfaq.txt) . Another useful source of information is the collection of FAQ articles posted frequently to the Usenet news groups comp.unix.questions, @@ -213,7 +213,7 @@ email(mail-server@rtfm.mit.edu) I have put together a user guide to complement the manual by explaining the most useful features of zsh in a more easy to read way. This can be found at the zsh web site: - url(http://zsh.sourceforge.net/Guide/)(http://zsh.sourceforge.net/Guide/) + url(https://zsh.sourceforge.io/Guide/)(https://zsh.sourceforge.io/Guide/) (As a method of reading the following in Emacs, you can type tt(\M-2 \C-x $) to make all the indented text vanish, then tt(\M-0 \C-x $) @@ -367,8 +367,8 @@ label(16) link(1.1)(11)) at: description( - mydit() url(http://zsh.sourceforge.net/Patches/) -(http://zsh.sourceforge.net/Patches/) + mydit() url(https://zsh.sourceforge.io/Patches/) +(https://zsh.sourceforge.io/Patches/) ) sect(I don't have root access: how do I make zsh my login shell?) @@ -2727,4 +2727,4 @@ notice appears in all copies of this documentation. Remember, however, that this document changes monthly and it may be more useful to provide a pointer to it rather than the entire text. A suitable pointer is "information on the Z-shell can be obtained on the World -Wide Web at URL http://zsh.sourceforge.net/". +Wide Web at URL https://zsh.sourceforge.io/". diff --git a/Etc/changelog2html.pl b/Etc/changelog2html.pl index 82416bff9..de6877d97 100755 --- a/Etc/changelog2html.pl +++ b/Etc/changelog2html.pl @@ -1,7 +1,7 @@ #!/usr/bin/perl -w # This programme turns the ChangeLog into changelog.html for display -# on the website. That lives at http://zsh.sourceforge.net/Etc/changelog.html. +# on the website. That lives at https://zsh.sourceforge.io/Etc/changelog.html. my $out = "changelog.html"; ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-24 12:09 ` Peter Stephenson @ 2021-05-24 18:26 ` Daniel Shahaf 0 siblings, 0 replies; 14+ messages in thread From: Daniel Shahaf @ 2021-05-24 18:26 UTC (permalink / raw) To: zsh-workers Peter Stephenson wrote on Mon, 24 May 2021 12:09 +00:00: > > On 24 May 2021 at 09:20 Peter Stephenson <p.w.stephenson@ntlworld.com> wrote: > > I've pushed the button: when we're quoting Sourceforge URLs then the new one is: > > > > https://zsh.sourceforge.io > > It's now live. Here are all the references I can see in the source > distribution. There are some references to "zsh.sf.net" too. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-24 8:20 ` Peter Stephenson 2021-05-24 12:09 ` Peter Stephenson @ 2021-05-24 17:39 ` Phil Pennock 2021-05-24 18:18 ` Bart Schaefer ` (2 more replies) 1 sibling, 3 replies; 14+ messages in thread From: Phil Pennock @ 2021-05-24 17:39 UTC (permalink / raw) To: zsh-workers 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. I'll take care of the web content I can touch now. -Phil ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-24 17:39 ` Phil Pennock @ 2021-05-24 18:18 ` Bart Schaefer 2021-05-24 18:23 ` Peter Stephenson 2021-05-24 19:43 ` website links (Re: Sourceforge -> https) Phil Pennock 2 siblings, 0 replies; 14+ messages in thread From: Bart Schaefer @ 2021-05-24 18:18 UTC (permalink / raw) To: Zsh hackers list On Mon, May 24, 2021 at 10:41 AM Phil Pennock <zsh-workers+phil.pennock@spodhuis.org> wrote: > > On 2021-05-24 at 09:20 +0100, Peter Stephenson wrote: > > > > 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 works for me with "http:". With "https:" it fails. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 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 2 siblings, 1 reply; 14+ messages in thread From: Peter Stephenson @ 2021-05-24 18:23 UTC (permalink / raw) To: zsh-workers 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 ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Sourceforge -> https 2021-05-24 18:23 ` Peter Stephenson @ 2021-05-24 18:57 ` Phil Pennock 0 siblings, 0 replies; 14+ messages in thread From: Phil Pennock @ 2021-05-24 18:57 UTC (permalink / raw) To: zsh-workers On 2021-05-24 at 19:23 +0100, Peter Stephenson wrote: > 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. No. That gives me a refusal to connect, it's a different IP to the .io and there simply isn't a listening service for https. This was 503 errors from sourceforge's side for the .net hostname, as stated. They seem to have resolved it (for now?). -Phil ^ permalink raw reply [flat|nested] 14+ messages in thread
* website links (Re: Sourceforge -> https) 2021-05-24 17:39 ` Phil Pennock 2021-05-24 18:18 ` Bart Schaefer 2021-05-24 18:23 ` Peter Stephenson @ 2021-05-24 19:43 ` Phil Pennock 2021-05-24 20:06 ` Bart Schaefer 2 siblings, 1 reply; 14+ messages in thread From: Phil Pennock @ 2021-05-24 19:43 UTC (permalink / raw) To: zsh-workers On 2021-05-24 at 13:39 -0400, Phil Pennock wrote: > I'll take care of the web content I can touch now. The www.zsh.org links were updated in the Ansible config and deployed. Those were the easy ones. :) The SF web repo was updated and deployed to live, twice. In the second pass, I looked at a whole bunch of http: links, outside of the patches/ tree, and updated what I had energy to update. For resources/forms included in the current page, this should prevent mixed-mode warnings and allow form submission to work once more. Well, I don't get big red warnings now, but I suspect it will take a little while for the search engines to index at the new URLs and be able to return site-scoped content. If anyone has setup webmaster console access with Google / Bing / Yandex and wants to trigger re-scans, that might be a good idea. (I don't know if Baidu users will care about this English-language content, but the last time I tried to setup webmaster console access in Baidu, it was rejecting foreign registrations so there's not much we can do here anyway, unless someone already has this setup?) YODL has moved home a couple of times, I chased through those breadcrumbs to the current live site. :) For SF, I went with the redirects to the project-by-name instead of by-number, but for the web git tree presentation I trimmed back to avoid hard-coding of branch names, so there will still be a redirect. The site <http://zshwiki.org> appears to be issuing an infinite redirect loop, so I commented out the links I found. There's some IBM DeveloperWorks articles which are not at the listed address any more, and some searching to find other articles by the same author found stuff in archival areas, but not as far back as the articles we link to. I've left those links broken, someone who is vaguely familiar with what they used to link to can perhaps dig out something on the Internet Archive worth linking to? -Phil ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: website links (Re: Sourceforge -> https) 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 0 siblings, 1 reply; 14+ messages in thread From: Bart Schaefer @ 2021-05-24 20:06 UTC (permalink / raw) To: Zsh hackers list On Mon, May 24, 2021 at 12:44 PM Phil Pennock <zsh-workers+phil.pennock@spodhuis.org> wrote: > > The site <http://zshwiki.org> appears to be issuing an infinite redirect > loop, so I commented out the links I found. Switching from http to https yields: There has been a critical error on this website. Learn more about troubleshooting WordPress. ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: website links (Re: Sourceforge -> https) 2021-05-24 20:06 ` Bart Schaefer @ 2021-05-24 20:16 ` Phil Pennock 0 siblings, 0 replies; 14+ messages in thread From: Phil Pennock @ 2021-05-24 20:16 UTC (permalink / raw) To: Bart Schaefer; +Cc: Zsh hackers list On 2021-05-24 at 13:06 -0700, Bart Schaefer wrote: > On Mon, May 24, 2021 at 12:44 PM Phil Pennock > <zsh-workers+phil.pennock@spodhuis.org> wrote: > > > > The site <http://zshwiki.org> appears to be issuing an infinite redirect > > loop, so I commented out the links I found. > > Switching from http to https yields: > > There has been a critical error on this website. > Learn more about troubleshooting WordPress. So the first thing I did when I saw a redirect loop was try to open the site in w3m -- I don't have persistent cookies there, and there are no browser plugins which might be forcing https. :) Also no scripting. It still ends up redirecting. Running `curl -v` shows: http://zshwiki.org --301--> http://zshwiki.org/home/ http://zshwiki.org/home/ --301--> https://zshwiki.org/ https://zshwiki.org/ --301--> http://zshwiki.org/home/ I can only get an error by trying <https://zshwiki.org/home/> directly. So yeah, I'm leaving that commented-out in the zsh site, pending evidence that the wiki still exists. I've no idea if it's been up since <https://www.reddit.com/r/zsh/comments/9catxz/zshwikiorg_down/> two years ago, at which point it had apparently been down for "at least a month". -Phil ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2021-05-24 20:16 UTC | newest] Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-05-21 15:23 Sourceforge -> https 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 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
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).