Description of problem: If you use guestfs_add_drive_opts, and the first parameter (the path) contains a query parameter, it is quoted: $ guestfish -x -v add "/?foo=bar" protocol:https server:test.example.com readonly:true : run ... libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libguestfs: command: run: \ -o backing_file=https://test.example.com/%3Ffoo=bar libguestfs: command: run: \ /tmp/libguestfsXUkwGI/overlay1 Note that the ? is quoted as %3F. This may or may not be a bug, but it means there is no way to provide a ?query in a URL when accessing a curl resource. Version-Release number of selected component (if applicable): libguestfs-1.29.46-1.fc23.x86_64 How reproducible: 100% Steps to Reproduce: 1. See above.
Isn't this somehow duplicated of bug #1092583, whose resolution (passing the query string separately, and reusing it for the protocols using it) would fix this bug as well?
If you mean we should add an extra parameter to add_drive_opts to hold the query string, analogous to the secret/password parameter, then yes I think that may be the right solution.