From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mx.mukund.org (mx.mukund.org [IPv6:2a01:4f8:252:2ade:1::78]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5BDE31F4D7 for ; Wed, 25 May 2022 02:19:11 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=mukund.org header.i=@mukund.org header.b="FCcyvRon"; dkim-atps=neutral Date: Wed, 25 May 2022 07:49:07 +0530 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail; t=1653445149; bh=1Tj/UIC8JMRouRcZQy3y/aUuE8NAoofSCwusZk7qCd4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FCcyvRoniV9sLeLUsN31oi4t+f0X02itrt3XG2s/XPBLtFzLHYB/vdQ9ETfC58C8G cU4O2PQxW1Y3ostT2WFJ7ZUfAJIG5uBa0NRlQ+M7ubSzCf63PnnVFS6ZogjpaeN8hQ 2aDMya7z8XQu+HnTlVUmgSXXGiZoanbkWAfRQrQBlNQjdrTVmZzp9cO6EuRWHjGys/ Apt5OBkNsgw4s4+spXywnciOazeujuuxzTv4CcPmREfGW3isBL5moU+dokD2Xlx3Vu eKAOGCBrVAznZkuFSwKsnWRH/qBusjHlQ+jZ+Idf+4yLxsPvyfoyGvtpPQRQkrzZ6l 4GLnjOEUcyBVw== From: Mukund Sivaraman To: Kyle Meyer Cc: meta@public-inbox.org Subject: Re: Message-ID not found Message-ID: References: <871qwiqz4b.fsf@kyleam.com> <87y1yqperi.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87y1yqperi.fsf@kyleam.com> List-Id: On Tue, May 24, 2022 at 09:44:33PM -0400, Kyle Meyer wrote: > > [...] > > 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? nginx is a reverse-proxy in front of public-inbox-httpd. I'll check if it breaks anything. Mukund