Currently, if you navigate to https://vim.org, nothing would show up. Instead, you have to go to https://www.vim.org. It's pretty common practice these days to do a redirect if the "www" version is the canonical one. E.g. if you navigate to https://google.com it does have a DNS entry, and it will simply do an HTTP 301 redirect to https://www.google.com.
Probably not a high priority issue, but it could be a little disorienting to people when you just type vim.org in the browser and then nothing shows up.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Another example of a website that does this is https://gnu.org/software/emacs/ which redirects to https://www.gnu.org/software/emacs/. 😅
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Closed #11259 as completed.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
This has been mentioned several times, but the maintainer of the DNS records says it doesn't work. I forgot the details.
Fortunately several browsers handle this if you type "vim.org".
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
This has been mentioned several times, but the maintainer of the DNS records says it doesn't work. I forgot the details.
Fortunately several browsers handle this if you type "vim.org".
Neither Firefox not Chromium on my system do this.
I'm pretty sure this can be made to work, one way or the other, even if it's just pointing vim.org to a simple HTML page with a meta refresh tag.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Neither Firefox not Chromium on my system do this.
Firefox(105) does, Chrome(105) doesn't on my system. Is there an option buried somewhere?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Hmm Firefox definitely didn't work for me before and now it seems to work. I have no idea why. I think it may depend on whether you have visited https://www.vim.org before.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Almost all DNS providers support this. At a minimum a redirect could be setup. This seems a weird thing to have broken for such a hugely popular project

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
This has been mentioned several times, but the maintainer of the DNS records says it doesn't work. I forgot the details.
Fortunately several browsers handle this if you type "vim.org".Neither Firefox not Chromium on my system do this.
I'm pretty sure this can be made to work, one way or the other, even if it's just pointing vim.org to a simple HTML page with a meta refresh tag.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
From the vim_dev mailing list, there's an effort to build a new website anyway, so this should hopefully be fixed as part of that effort. This should really be fixed at the DNS / server configuration level instead of relying on browser behaviors.
https://groups.google.com/g/vim_announce/c/cUzmP2xxecM/m/tEht7Pz5HAAJ
—
Reply to this email directly, view it on GitHub.
You are receiving this because you commented.![]()
I can recommend DNSimple (not affiliated) as a cheap and flexible provider that supports "alias" records that will handle the redirects for you.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you commented.![]()