From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexander Zeidler <a.zeidler@proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH v2 docs] sysadmin: add section 'Firmware Updates' and references
Date: Thu, 21 Sep 2023 15:50:18 +0200 [thread overview]
Message-ID: <2dc9d532-c86e-431c-9bf0-61d5525ebf2b@proxmox.com> (raw)
In-Reply-To: <6efbf465-4ad6-40d1-b2fc-5ca71068766c@proxmox.com>
Am 21/09/2023 um 15:17 schrieb Thomas Lamprecht:
> Oh, and this made me think that it would be nice to have a test for
> checking all linked URLs, i.e., make a request and see if that
> immediately return HTTP OK 200 code, otherwise output the url as
> possibly broken or in need of update. This could be a simple make
> target, albeit not sure what tooling to use for scan for urls and
> query them, some simple perl script might be enough.
Fabian pointed me to mlc [0], and with that we already found two dead
links (now fixed), and also that both ceph.com and ceph.io are broken if
a user-agent doesn't sends a "Accept-Language" header [1], while not even
providing multiple languages – can't make this up..
[0]: https://crates.io/crates/mlc
[1]: https://tracker.ceph.com/issues/51364
prev parent reply other threads:[~2023-09-21 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:21 [pve-devel] " Alexander Zeidler
2023-09-11 10:27 ` Alexander Zeidler
2023-09-20 9:59 ` Dominik Csapak
2023-09-20 13:26 ` Thomas Lamprecht
2023-09-21 13:17 ` [pve-devel] applied: " Thomas Lamprecht
2023-09-21 13:50 ` Thomas Lamprecht [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=2dc9d532-c86e-431c-9bf0-61d5525ebf2b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=a.zeidler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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