From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
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 16:54:25 -0400 [thread overview]
Message-ID: <20250411-talented-elegant-earthworm-e741ef@lemur> (raw)
In-Reply-To: <20250410103037.GCZ_edzWEQSfxV880T@fat_crate.local>
On Thu, Apr 10, 2025 at 12:30:37PM +0200, Borislav Petkov wrote:
> +1
>
> I have a script which tests whether a lore link: URL I'm adding to patches, is
> correct. I.e. whether
>
> https://lore.kernel.org/r/<Message-ID>
>
> can be read.
>
> What would be the suggested thing to do in such cases?
You can continue doing it -- this is a lightweight operation. Just use a HEAD
request instead of a GET request.
E.g.:
[[ $(curl -o/dev/null -sIw '%{response_code}' https://lore.kernel.org/all/20250411201912.2872-1-annie.li@oracle.co/) -gt 200 ]] && echo "ivalid" || echo "valid"
-K
next prev parent reply other threads:[~2025-04-11 20:54 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 [this message]
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
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=20250411-talented-elegant-earthworm-e741ef@lemur \
--to=konstantin@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=cel@kernel.org \
--cc=da.gomez@kernel.org \
--cc=kdevops@lists.linux.dev \
--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