I made this change on master branch, but am reconsidering it. Right now, the meaning of "use_https" is for how s3cmd communicates to an S3 server. This change expands that meaning. Furthermore, AWS S3's wildcard cert doesn't work well for HTTPS URLs of the form https://<bucket-in-dns-name-format>/path/to/object. Not that you can't use it, but the user is given a browser warning that the certificate doesn't match.
I'm inclined to revert the change, and let any tool that consumes the result of the signurl command to simply s/^http/https/ itself if so desired, knowing the limitations of the HTTPS wildcard cert. It doesn't affect the rest of the signed URL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made this change on master branch, but am reconsidering it. Right now, the meaning of "use_https" is for how s3cmd communicates to an S3 server. This change expands that meaning. Furthermore, AWS S3's wildcard cert doesn't work well for HTTPS URLs of the form https://<bucket-in-dns-name-format>/path/to/object. Not that you can't use it, but the user is given a browser warning that the certificate doesn't match.
I'm inclined to revert the change, and let any tool that consumes the result of the signurl command to simply s/^http/https/ itself if so desired, knowing the limitations of the HTTPS wildcard cert. It doesn't affect the rest of the signed URL.
reverted.