From: Michal Fox <me@dualfroz.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH http-server 0/2] apiserver: make multipart upload parsing more RFC compliant
Date: Fri, 25 Sep 2026 05:34:21 +0000 [thread overview]
Message-ID: <20260925053423.7-1-me@dualfroz.com> (raw)
two small fixes for the upload parser, both for things the RFCs allow
and real clients send: a quoted boundary (#6887) and unquoted
name/filename values, which .NET and PowerShell use (#7389).
tested by running curl, quoted-boundary and .NET style bodies through
file_upload_multipart() with different chunk sizes. curl behaves as
before, the other two now parse and the file comes out intact
Michal Fox (2):
fix #6887: apiserver: accept quoted multipart boundary
fix #7389: apiserver: accept unquoted multipart parameter values
src/PVE/APIServer/AnyEvent.pm | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-28 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 5:34 Michal Fox [this message]
2026-09-25 5:34 ` [PATCH http-server 1/2] fix #6887: apiserver: accept quoted multipart boundary Michal Fox
2026-09-25 5:34 ` [PATCH http-server 2/2] fix #7389: apiserver: accept unquoted multipart parameter values Michal Fox
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=20260925053423.7-1-me@dualfroz.com \
--to=me@dualfroz.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