Hi, This series adds the support for S3 presigned URLs that only allow HTTP GET requests. While working on this I also stumbled upon a deadlock with concurrent I/O and slipped the fix here. Over the years there was already an attempt to support these kinds of URLs[1] and at least one report of a user in need of the feature[2].
Unfortunately S3 only allows a presigned URL to live up to 7 days so we can't really put an example with a stable URL on the commit message but here is a presigned URL for the archlinux cloud image[3] that will expire in ~7 days. Cheers, Antoine [1]: https://lore.kernel.org/qemu-devel/110120539.4133.de5ac8a5-69d1-4f59-9540-4a679771a547.open-xcha...@ox.pcextreme.nl/ [2]: https://lore.kernel.org/qemu-devel/[email protected]/ [3]: http://test-presigned.s3.fr-par.scw.cloud/Arch-Linux-x86_64-cloudimg.qcow2?AWSAccessKeyId=SCWDHE3XBQGZFV282QKG&Expires=1772551595&Signature=fqADX1DJvEKcC8iEeoZpssYSkTI%3D --- Changes in v2: - New patch (2) that refactors the http(s) QAPI types - Specify and reword what happens when using 'force-range' with an HTTP server that doesn't support the feature - Document that 'force-range' defaults to false in QAPI - Fix a few typos - Regen presigned URL[3] - Link to v1: https://lore.kernel.org/qemu-devel/[email protected] --- Antoine Damhet (3): block/curl: fix concurrent completion handling qapi: block: Refactor HTTP(s) common arguments block/curl: add support for S3 presigned URLs block/curl.c | 115 ++++++++++++++++---------- block/trace-events | 1 + docs/system/device-url-syntax.rst.inc | 6 ++ qapi/block-core.json | 22 +++-- 4 files changed, 90 insertions(+), 54 deletions(-) -- 2.53.0
