From: Ihor Radchenko <yantar92@gmail.com>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: emacs-orgmode@gnu.org, Tim Cross <theophilusx@gmail.com>
Subject: Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)]
Date: Sun, 03 Jul 2022 19:50:34 +0800 [thread overview]
Message-ID: <878rpah0tx.fsf@localhost> (raw)
In-Reply-To: <m2sfni5xcb.fsf@me.com>
Rudolf Adamkovič <salutis@me.com> writes:
> I noticed that the Org documentation server gives 404 Not Found for a
> large number of links published all over the internet because (1) it
> parses URLs case-sensitively and (2) the case has changed at some point.
> I stumble upon such 404s errors daily. See, for instance, the link to
> Column Groups documentation in this Stack Overflow answer:
>
> https://stackoverflow.com/a/8570307/1306956.
>
> I know that Org does not compete for popularity, but for the people
> getting familiar with it, this issue might cause a lot of headaches for
> no good reason.
Thanks for the heads up!
I am CCing Tim Cross. He is currently doing some work on our server. He
is more likely to know how to fix this.
Best,
Ihor
next prev parent reply other threads:[~2022-07-03 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:01 [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)] Rudolf Adamkovič
2022-07-03 11:50 ` Ihor Radchenko [this message]
2022-07-03 12:23 ` Tim Cross
2022-07-03 14:01 ` Ihor Radchenko
2022-07-03 16:48 ` Max Nikulin
2022-07-03 21:30 ` Tim Cross
2022-07-04 12:10 ` Ihor Radchenko
2022-07-04 12:27 ` Tim Cross
2022-07-04 12:58 ` Ihor Radchenko
2022-07-04 17:24 ` Max Nikulin
2022-07-04 22:37 ` Tim Cross
2022-07-05 2:39 ` Max Nikulin
2022-07-05 2:54 ` Tim Cross
2022-07-05 4:22 ` Max Nikulin
2022-07-05 4:36 ` Tim Cross
2022-07-05 5:11 ` Ihor Radchenko
2022-09-18 9:06 ` Bastien
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rpah0tx.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=salutis@me.com \
--cc=theophilusx@gmail.com \
/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.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).