From: Ihor Radchenko <yantar92@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: "Rudolf Adamkovič" <salutis@me.com>,
emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)]
Date: Sun, 03 Jul 2022 22:01:54 +0800 [thread overview]
Message-ID: <87wncufg6l.fsf@localhost> (raw)
In-Reply-To: <87wncu8iuw.fsf@gmail.com>
Tim Cross <theophilusx@gmail.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.
>> ...
>> 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.
>
> Well I'm not sure what is the correct 'fix'. As far as I am aware, the
> file part of URI are case sensitive and always have been. The web server
> does not have a simple configuration switch to turn on case insensitive
> URLs. If we want the web server to treat them as case insensitive, then
> we have to add costly regular expression rewrite rules to the URLs sent to the
> server. We would also need to verify this won't break anything - it is
> possible some links depend on the server treating URLs as case
> sensitive.
> ...
> BTW this is not something I have the access to change as it would
> involve changes to the actual web server configuration. It isn't
> something which can be 'fixed' at the Org level.
Then, I am also CCing Bastien.
As an idea, the "fix" can be creating symlinks to alternative file
names. But we first need to figure out the difference between old/new
naming schemes.
> It isn't clear to me what the chain of events have been here. Is it that
> we changed the case on our server or is it simply people have put out
> link which arfe wrong?
>
> Is this the result of some change in the way the HTML manual is
> generated or a change in how org generates HTML or is this just the
> result of people posting the wrong URL?
I have a suspicion that it might have something to do with texinfo
versions. AFAIU, Org manual pages are generated using makeinfo and it is
makeinfo that it responsible for the file name generation. (see
https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#HTML-Splitting)
Probably, the naming scheme or some configuration variables have changed
in different versions of texinfo.
Best,
Ihor
next prev parent reply other threads:[~2022-07-03 14:01 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
2022-07-03 12:23 ` Tim Cross
2022-07-03 14:01 ` Ihor Radchenko [this message]
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=87wncufg6l.fsf@localhost \
--to=yantar92@gmail.com \
--cc=bzg@gnu.org \
--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).