From: "Luck, Tony" <tony.luck@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Daniel Gomez <da.gomez@kernel.org>,
users@kernel.org, Luis Chamberlain <mcgrof@kernel.org>,
Chuck Lever <cel@kernel.org>,
kdevops@lists.linux.dev
Subject: Re: Forbidden requests for kernel.org/releases.json
Date: Fri, 11 Apr 2025 11:23:12 -0700 [thread overview]
Message-ID: <Z_leEK-rwML6WRiJ@agluck-desk3> (raw)
In-Reply-To: <20250410-prophetic-elegant-fossa-a210fb@lemur>
On Thu, Apr 10, 2025 at 08:45:30AM -0400, Konstantin Ryabitsev wrote:
> On Thu, Apr 10, 2025 at 10:05:28AM +0200, Daniel Gomez wrote:
> > We've started encountering "HTTP Error 403: Forbidden" errors in kdevops
> > when querying https://www.kernel.org/releases.json from our CI environments/
> > deployments. We're using a Python script with the urllib library to fetch the
> > latest kernel release information [1].
>
> Yes, I'm trying to deal with bots who don't identify themselves. We're seeing
> many requests per second from user-agents like "python-requests/x.x" or
> "Python-urllib/x.x" or "Java/x.x" etc, and it's impossible for us to tell good
> bots from bad bots if they don't identify themselves properly.
>
> > * What is the recommended approach for automated tools to access
> > kernel.org/releases.json?
>
> Set your user-agent to something like:
>
> "kdevops-ci/{version} (contact@address.here)"
Would it help things if you just delayed response to *every*
query by a couple of seconds?
While I love it that lore.kernel.org answers my queries more
or less instantly, my user experience wouldn't suffer significantly
if I had to wait for a short (to humans) but long (to bots) time.
-Tony
prev parent reply other threads:[~2025-04-11 18:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 8:05 Forbidden requests for kernel.org/releases.json Daniel Gomez
2025-04-10 10:30 ` Borislav Petkov
2025-04-10 12:09 ` Daniel Gomez
2025-04-11 20:54 ` Konstantin Ryabitsev
2025-04-15 9:01 ` Borislav Petkov
2025-10-13 13:15 ` Borislav Petkov
2025-10-13 15:19 ` Theodore Ts'o
2025-10-14 16:10 ` Kees Cook
2025-04-10 12:45 ` Konstantin Ryabitsev
2025-04-11 14:18 ` Theodore Ts'o
2025-04-11 15:25 ` Konstantin Ryabitsev
2025-04-11 16:48 ` James Bottomley
2025-04-11 16:59 ` Laurent Pinchart
2025-04-11 17:00 ` Konstantin Ryabitsev
2025-04-11 17:13 ` James Bottomley
2025-04-11 20:38 ` Konstantin Ryabitsev
2025-04-12 2:19 ` Theodore Ts'o
2025-04-11 20:56 ` Luis Chamberlain
2025-04-11 21:04 ` Konstantin Ryabitsev
2025-04-11 23:37 ` Luis Chamberlain
2025-04-11 20:08 ` Jonathan Corbet
2025-04-11 17:09 ` Theodore Ts'o
2025-04-11 18:23 ` Luck, Tony [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z_leEK-rwML6WRiJ@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=cel@kernel.org \
--cc=da.gomez@kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=konstantin@linuxfoundation.org \
--cc=mcgrof@kernel.org \
--cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox