From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Nicolas Frey <n.frey@proxmox.com>
Subject: [pve-devel] applied: [PATCH 0/2] improve error message when accessing a directory
Date: Wed, 14 Jan 2026 15:03:03 +0100 [thread overview]
Message-ID: <176839937736.244740.13439284166175838844.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251015080330.45927-1-n.frey@proxmox.com>
On Wed, 15 Oct 2025 10:03:28 +0200, Nicolas Frey wrote:
> I ran into this when I accidentally went to the path /pve-docs/api-viewer
> instead of /pve-docs/api-viewer/index.html, where I got this error:
>
> `unable to detect content type at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 499.`
>
> Which IMO was not very telling of the underlying mistake I had made.
> This patch aims to improve this error message by checking if the
> queried file is a directory and returning a more descriptive
> message to the user.
>
> [...]
Applied, both patches, thanks!
[1/2] apiserver: fix typo
commit: a6f85919f5776e32eab2091f027d353f6fb1051f
[2/2] apiserver: check if file is directory before opening
commit: 5c9e4ea773364bdb7ae0e2faec5750fe58129a47
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-14 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 8:03 [pve-devel] " Nicolas Frey
2025-10-15 8:03 ` [pve-devel] [PATCH 1/2] apiserver: fix typo Nicolas Frey
2025-10-15 8:03 ` [pve-devel] [PATCH 2/2] apiserver: check if file is directory before opening Nicolas Frey
2026-01-14 14:03 ` Fiona Ebner [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=176839937736.244740.13439284166175838844.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=n.frey@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