From: Mukund Sivaraman <muks@mukund.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: Message-ID not found
Date: Wed, 25 May 2022 05:29:27 +0530 [thread overview]
Message-ID: <Yo1xX+MNTMBmPITl@d1> (raw)
In-Reply-To: <871qwiqz4b.fsf@kyleam.com>
Hi Kyle
On Tue, May 24, 2022 at 07:39:32PM -0400, Kyle Meyer wrote:
> Mukund Sivaraman writes:
>
> > I'm testing public-inbox with a "test-list" to try to provide a HTTP
> > interface to mailing list archives. I'm using stock
> > public-inbox-1.7.0-2.fc35.noarch on Fedora 35.
> >
> > List emails are injected by public-inbox-mda. public-inbox-httpd
> > displays an error at this URL:
> >
> > https://inbox.banu.com/test-list/Yo1VM9+M%252FsYJIZkN@d1/T/
>
> What's the source of this URL?
In the thread index at: https://inbox.banu.com/test-list/
The 2nd thread with subject "About Pluto" links to:
https://inbox.banu.com/test-list/Yo1VM9+M%2FsYJIZkN@d1/T/#t
The webpage at that URL displays the
"Message-ID <Yo1VM9+M/sYJIZkN@d1/T> not found" error.
In this case, there is just one escape "%2F" in the URL for '/', and
from the error message it has correctly unescaped the Message-ID except
for the trailing "/T".
Could there be a bug in how the '/' is treated as a separator in
public-inbox-httpd?
Mukund
next prev parent reply other threads:[~2022-05-24 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:31 Message-ID not found Mukund Sivaraman
2022-05-24 23:39 ` Kyle Meyer
2022-05-24 23:59 ` Mukund Sivaraman [this message]
2022-05-25 1:44 ` Kyle Meyer
2022-05-25 2:19 ` Mukund Sivaraman
2022-05-25 6:05 ` Mukund Sivaraman
2022-05-25 9:00 ` 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=Yo1xX+MNTMBmPITl@d1 \
--to=muks@mukund.org \
--cc=kyle@kyleam.com \
--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).