Re: Message-ID not found

[Kyle Meyer <kyle@kyleam.com>]

Mukund Sivaraman writes:

> On Tue, May 24, 2022 at 07:39:32PM -0400, Kyle Meyer wrote:
[...]
>> > 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

Okay, so that link looks good.  And then when I follow the link...

> The webpage at that URL displays the
> "Message-ID <Yo1VM9+M/sYJIZkN@d1/T> not found" error.

... I see the "Message-ID <Yo1VM9+M/sYJIZkN@d1/T> not found" error you
describe.

I pulled in your inbox and ran public-inbox-httpd (v1.7.0 and v1.8.0)
locally:

  /test-list/Yo1VM9+M%2FsYJIZkN@d1/T/#t

And then when I follow that link.I see the message for
<Yo1VM9+M/sYJIZkN@d1>, as expected.  Hmm.

> [...]
> Could there be a bug in how the '/' is treated as a separator in
> public-inbox-httpd?

Sure, though my guess is that there is something more setup-specific
going on because 1) I don't see it when I try the inbox locally and 2) I
think slashes are common enough in the wild yet I don't recall seeing
similar reports for public-inbox.org inboxes, lore.kernel.org inboxes,
or the inboxes that I host.

As an example, at https://lore.kernel.org/git/?t=20220525002051 the link
for "[PATCH v5 02/17] pack-mtimes: support reading .mtimes files" is to

  https://lore.kernel.org/git/Yo1aaLDmPKJ5%2Frh5@nand.local/T/#u

I was able to successfully follow that to the message.

Could there be something in your setup that's doing the second round of
percent-encoding?