From: Willy Tarreau <w@1wt.eu>
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: Sat, 22 Jul 2023 20:47:09 +0200 [thread overview]
Message-ID: <20230722184709.GA17936@1wt.eu> (raw)
In-Reply-To: <7pcrdb6rgkmnfk5nukr4q7brpdmzrjon5zjmc66r2xvqan7kyc@oe3ip5kmtuiy>
Hi Maxime,
On Sat, Jul 22, 2023 at 07:12:33PM +0200, Maxime Ripard wrote:
> Hi,
>
> I've been trying to fetch an mbox from lore with an arbitrary search request.
>
> I could fetch it fine using curl with the following example:
>
> curl -XPOST -H "Content-Length:0" -OJ "http://lore.kernel.org/linux-clk/?q=d:1.week.ago..&x=m"
>
> This returns a gzip'd mbox, everything's fine.
Note that when I do this I get redirected to the https URL and when I
use it, then it works.
> def try_url_redirect(url):
> headers={"Content-Length": "0"}
> params={"q": "d:1.week.ago..", "x": "m"}
>
> s = Session()
>
> req = Request('POST', url, headers=headers, params=params)
> p = req.prepare()
I don't know about this part in python, but are you certain that
it's not trying to pass the params in the request body ? It would
seem natural to me since you've asked for a POST. In your curl
request, you're not sending arguments as part of the body but as
a query string with an empty body.
It would be useful to strace the output (use http:// to make it
easier) to verify, because I really don't trust the debugging
output which possibly just reassembles the URL as if it were a
GET except that it's not that. With curl (in HTTP) it's what the
request says at least:
20:43:22.246844 sendto(5, "POST /linux-clk/?q=d:1.week.ago..&x=m HTTP/1.1\r\nHost: lore.kernel.org\r\nUser-Agent: curl/7.81.0\r\nAccept: */*\r\nContent-Length:0\r\n\r\n", 129, MSG_NOSIGNAL, NULL, 0) = 129
You should try to concatenate your arguments just at the end of
the URL and really send nothing with the POST.
Hoping this helps a little bit,
Willy
next prev parent reply other threads:[~2023-07-22 18:55 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 [this message]
2023-07-22 22:34 ` Rob Herring
2023-07-24 8:07 ` Maxime Ripard
2023-07-23 1:36 ` Eric Wong
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=20230722184709.GA17936@1wt.eu \
--to=w@1wt.eu \
--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.