From: Eric Wong <e@80x24.org>
To: Mukund Sivaraman <muks@mukund.org>
Cc: Kyle Meyer <kyle@kyleam.com>, meta@public-inbox.org
Subject: Re: Message-ID not found
Date: Wed, 25 May 2022 09:00:47 +0000 [thread overview]
Message-ID: <20220525090047.GA17143@dcvr> (raw)
In-Reply-To: <Yo3HQs5UOBs4okyd@d1>
Mukund Sivaraman <muks@mukund.org> wrote:
> 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.
Thanks both. Fwiw, the long-term plan is to allow public-inbox-httpd
to replace nginx entirely to avoid configuration pitfalls like this.
prev parent reply other threads:[~2022-05-25 9:00 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
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 [this message]
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=20220525090047.GA17143@dcvr \
--to=e@80x24.org \
--cc=kyle@kyleam.com \
--cc=meta@public-inbox.org \
--cc=muks@mukund.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).