From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <muks@mukund.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS24940 144.76.0.0/16
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 [144.76.148.120])
	(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 9B1EA1F4D7
	for <meta@public-inbox.org>; Wed, 25 May 2022 06:06:01 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=mukund.org header.i=@mukund.org header.b="nFyflJg4";
	dkim-atps=neutral
Date: Wed, 25 May 2022 11:35:54 +0530
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mukund.org; s=mail;
	t=1653458759; bh=4BDRqqzxrs+zzQ/iqT1ksPkHAcaF4q7WvKoywVWyoPg=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=nFyflJg4hWd45Vh1qypdJsSPIRNPzI2W83L++clcb6kzI6yc0uVFiGgtO+Sq9wtmY
	 TNK5MwkQnyapb5m5383XhqiLna450fivKuQk5UavgJiy9ILG8Is8aeu3qOpKXVmCNN
	 ncPTRbSPdPdx6aPum+mtD5rVXSzS2sd0XkdOV5hPK/aSndg0UXKkU7nsacWvgoKRVi
	 w/gmFketOpsvTxhnDoGNX2pNr4n3l8acIszG4dFKRKq1GJ+5hoo5v6U4Z/tjBK+NCm
	 aB9ey4ddCwvR3K/qvXpywYTUB0MvQ9MHaD++Wy/7KHVolKbmwxBOWh0zSfOwt1RJbq
	 jP6f2HQjuWdaA==
From: Mukund Sivaraman <muks@mukund.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: Message-ID not found
Message-ID: <Yo3HQs5UOBs4okyd@d1>
References: <Yo1c3oSzBKsRgQ4z@d1>
 <871qwiqz4b.fsf@kyleam.com>
 <Yo1xX+MNTMBmPITl@d1>
 <87y1yqperi.fsf@kyleam.com>
 <Yo2SGwB54Kh4c8nX@d1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Yo2SGwB54Kh4c8nX@d1>
List-Id: <meta.public-inbox.org>

Hi Kyle

On Wed, May 25, 2022 at 07:49:07AM +0530, Mukund Sivaraman wrote:
> > 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.

It was a problem with the nginx reverse-proxy config. I updated it, and
it works now. Thank you for checking, and esp. pointing out that it
worked directly with public-inbox-httpd.

For anyone else who searches and finds this thread, a working nginx
configuration with proxy_pass follows, where proxy_pass must not include
a trailing '/':

# create an upstream
upstream inbox_proxy_backend {
    server unix:/run/inbox/inbox.sock fail_timeout=0;
    keepalive 32;
}

server {
    # other server config
    # ...

    location / {
        proxy_pass http://inbox_proxy_backend;
        include proxy_params;
    }
}

		Mukund