From: Tim Landscheidt <tim@tim-landscheidt.de>
To: emacs-orgmode@gnu.org
Subject: Re: Some links in online manual do not work
Date: Wed, 05 Oct 2022 17:48:30 +0000 [thread overview]
Message-ID: <87mtaakvpt.fsf@vagabond.tim-landscheidt.de> (raw)
In-Reply-To: 86fsg6szf6.fsf@gmail.com
Tim Cross <theophilusx@gmail.com> wrote:
>> at https://orgmode.org/manual/HTML-Export.html, the links
>> for the first five (5) and the last two (2) subsections
>> work, the links for:
>> - "Headlines in HTML export"
>> (https://orgmode.org/manual/Headlines-in-HTML-export.html)
>> - "Links in HTML export"
>> (https://orgmode.org/manual/Links-in-HTML-export.html)
>> - "Tables in HTML export"
>> (https://orgmode.org/manual/Tables-in-HTML-export.html)
>> - "Images in HTML export"
>> (https://orgmode.org/manual/Images-in-HTML-export.html)
>> - "Math formatting in HTML export"
>> (https://orgmode.org/manual/Math-formatting-in-HTML-export.html)
>> - "Text areas in HTML export"
>> (https://orgmode.org/manual/Text-areas-in-HTML-export.html)
>> however all return "301 Moved Permanently", pointing back to
>> "HTML-Export.html".
>> The fact that all failing links are named
>> "Something-in-HTML-export.html" might suggest an issue with
>> the webserver configuration.
> This looks like the nginx case issue again.
> I've looked at this and there does not seem to be any 'clean' way to fix
> this which also doesn't have significant processing overhead or a
> maintenance burden.
> I wonder if it would be worthwhile adding an option to HTML export which
> would force all link targets and exported filenames to lower case,
> thereby avoiding issues on platforms and with web servers which have
> different positions wrt case sensitivity?
Is the nginx configuration/webserver setup documented some-
where?
Tim
next prev parent reply other threads:[~2022-10-05 17:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 20:00 Some links in online manual do not work Tim Landscheidt
2022-10-02 21:04 ` Tim Cross
2022-10-03 3:52 ` Ihor Radchenko
2022-10-05 17:48 ` Tim Landscheidt [this message]
2022-10-06 4:17 ` Ihor Radchenko
2022-10-06 12:14 ` Tim Landscheidt
2022-10-07 15:33 ` Bastien Guerry
2022-10-07 19:50 ` Tim Landscheidt
2022-10-08 6:28 ` Ihor Radchenko
2022-10-08 12:37 ` Max Nikulin
2022-10-11 5:37 ` Bastien
2022-10-11 6:57 ` Max Nikulin
2022-10-11 7:57 ` Bastien
2022-10-11 8:33 ` Max Nikulin
2022-10-11 9:09 ` Bastien
2022-10-11 16:51 ` Max Nikulin
2022-10-11 17:06 ` Bastien Guerry
2022-10-12 3:06 ` Max Nikulin
2022-10-12 4:11 ` Bastien Guerry
2022-10-12 5:14 ` Max Nikulin
2022-10-16 12:11 ` Tim Landscheidt
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=87mtaakvpt.fsf@vagabond.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=emacs-orgmode@gnu.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.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).