From: Eric Wong <e@80x24.org>
To: Maxime Ripard <mripard@redhat.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: Fetching an mbox from lore
Date: Sun, 23 Jul 2023 01:36:24 +0000 [thread overview]
Message-ID: <20230723013624.M167248@dcvr> (raw)
In-Reply-To: <7pcrdb6rgkmnfk5nukr4q7brpdmzrjon5zjmc66r2xvqan7kyc@oe3ip5kmtuiy>
Maxime Ripard <mripard@redhat.com> wrote:
> LORE_URL = "https://lore.kernel.org/linux-clk"
That should be:
LORE_URL = "https://lore.kernel.org/linux-clk/"
The trailing slash is critical. The URL format of public-inbox
enforces it to ensure mirroring via `wget --recursive' works.
> Trying to connect to https://lore.kernel.org/linux-clk?q=d%3A1.week.ago..&x=m
> Redirecting to http://lore.kernel.org/linux-clk/?q=d%3A1.week.ago..&x=m
> Trying to connect to http://lore.kernel.org/linux-clk/?q=d%3A1.week.ago..&x=m
> Redirecting to https://lore.kernel.org/linux-clk/?q=d%3A1.week.ago..&x=m
I'm not sure why lore goes HTTPS => HTTP, though...
lore probably needs to have Plack::Middleware::ReverseProxy
installed and configure the reverse proxy (likely nginx) to set
X-Forwarded-HTTPS:1 or X-Forwarded-Proto:https headers
> If I do allow redirects, then requests will issue a GET on the new
> location and I'll end up with the HTML webpage of that request.
>
> Am I trying to do something not supported here, or is it supposed to
> work and my script is wrong for some reason?
I can't remember off the top of my head how redirect rules ought
to work for non-GET requests, but avoiding redirects is usually
prudent
next prev parent reply other threads:[~2023-07-23 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 17:12 Fetching an mbox from lore Maxime Ripard
2023-07-22 18:47 ` Willy Tarreau
2023-07-22 22:34 ` Rob Herring
2023-07-24 8:07 ` Maxime Ripard
2023-07-23 1:36 ` Eric Wong [this message]
2023-07-24 8:06 ` Maxime Ripard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230723013624.M167248@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=mripard@redhat.com \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.