From: Max Nikulin <manikulin@gmail.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Some links in online manual do not work
Date: Sat, 8 Oct 2022 19:37:43 +0700 [thread overview]
Message-ID: <6559964f-1d94-913a-04b4-a911fa30ae38@gmail.com> (raw)
In-Reply-To: <87mta7fm5l.fsf@vagabond.tim-landscheidt.de>
On 08/10/2022 02:50, Tim Landscheidt wrote:
> Bastien Guerry <bzg@gnu.org> wrote:
>
>> https://git.sr.ht/~bzg/worg/tree/master/item/nginx.conf
>
> Thanks. Assuming the relevant line is:
>
> | rewrite HTML-export.html HTML-Export.html permanent;
>
> looking at
> http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite
> suggests that this will match any URL that contains the
> string "HTML-export.html", i. e. the regular expression is
> not anchored anywhere.
>
> So if that regular expression is intended to match on URLs
> that end in "/HTML-export.html", an (untested) fix would be
> something along the lines of:
>
> | rewrite /HTML-export\.html$ HTML-Export.html permanent;
Bastien, I have not tried full configuration, but after a quick check I
believe that it is a reasonable suggestion. It prevents 301 redirection
from valid URLs like
https://orgmode.org/manual/Links-in-HTML-export.html
to
https://orgmode.org/manual/HTML-Export.html
In addition I would consider
location /manual/ {
}
around the rewrite directives to prevent unintentional false positives
in e.g. worg.
P.S. Workarounds:
M-: (info "(org) Links in HTML Export")
https://orgmode.org/org.html#HTML-Export
next prev parent reply other threads:[~2022-10-08 12:39 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
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 [this message]
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=6559964f-1d94-913a-04b4-a911fa30ae38@gmail.com \
--to=manikulin@gmail.com \
--cc=bzg@gnu.org \
--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).