From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: meta@public-inbox.org
Subject: Bug related to (maybe?) / in Message-Id
Date: Thu, 16 Feb 2023 22:05:46 +0100 [thread overview]
Message-ID: <20230216210546.eo73kyzvtzaxwxko@pengutronix.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Hello,
The mail by Alexander Dahl that is (currently) the first hit on
https://lore.ptxdist.org/ptxdist/?q=ptxd_make_world_compile_commands_filter
results in a 404 when I follow the link.
The original mail has
Message-ID: <Y+07h0l/zJJAgs9s@falbala.internal.home.lespocky.de>
and the corresponding link is:
https://lore.ptxdist.org/ptxdist/Y+07h0l%2FzJJAgs9s@falbala.internal.home.lespocky.de/
I noticed this on public-inbox 1.8.0-1~bpo11+1 from Debian, upgrading to
1.9.0-1~bpo11+1 didn't help.
Other mails with / in Message-Id are not accessible either, I tested
with:
YyHu/412LT8uQTy1@lenoch
Y0/5xdFZO3u0952+@lenoch
I also wonder why these mails yield the webserver's 404 page and not the
one provided by the public-inbox cgi?!
Is this a problem in public-inbox, or is the apache configuration
somehow borked? Any hints welcome.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-16 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 21:05 Uwe Kleine-König [this message]
2023-02-16 21:36 ` Bug related to (maybe?) / in Message-Id Eric Wong
2023-02-17 8:52 ` Uwe Kleine-König
2023-02-17 10:28 ` Eric Wong
2023-02-17 10:32 ` [PATCH] TODO: handle more cases of unencoded slashes Eric Wong
2023-02-17 11:08 ` [PATCH] public-inbox.cgi(1): Mention AllowEncodedSlashes for Apache setups Uwe Kleine-König
2023-02-17 13:15 ` Eric Wong
2023-02-18 17:58 ` Bug related to (maybe?) / in Message-Id Thomas Weißschuh
2023-02-18 18:06 ` Thomas Weißschuh
2023-03-07 8:31 ` Eric Wong
2023-03-07 22:30 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230216210546.eo73kyzvtzaxwxko@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=meta@public-inbox.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.
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).