[Cyberduck-trac] [Cyberduck] #9781: URL creation for custom domains on AWS CloudFront

[Cyberduck]

#9781: URL creation for custom domains on AWS CloudFront
-------------------------+-------------------
    Reporter:  aljoscha  |      Owner:
        Type:  defect    |     Status:  new
    Priority:  normal    |  Milestone:
   Component:  s3        |    Version:  5.2.2
    Severity:  normal    |   Keywords:
Architecture:  Intel     |   Platform:
-------------------------+-------------------
 1. we uploaded files to S3 to a bucket name "shared.jovo.to"
 The https URL for a file (created by Cyberduck) then is something like
 https://shared.jovo.to.s3.amazonaws.com/my-file.jpg

 2. now we want to use our own domain (shared.jovo.to), so we CNAME
 shared.jovo.to to shared.jovo.to.s3.amazonaws.com. and put
 http://shared.jovo.to into the Setting "Web URL"
 The http URL now is
 http://shared.jovo.to/my-file.jpg (fine!)
 but the https URL is
 https://shared.jovo.to.s3.amazonaws.com/my-file.jpg
 which kind of works, but gives a security warning, because serving files
 from S3 with own SSL certificate is not possible and so the domain and the
 default AES S3 certificate do not match.
 Nothing much Cyberduck can do about this.

 3. we put a Cloudfront distribution in front of the bucket change the
 CNAME to point to our CloudFront distribution and upload our certificate
 in CloudFront. Now the HTTPS URL if the file really should be
 https://shared.jovo.to/my-file.jpg (which works fine and shows the correct
 certificate) but Cyberduck still gives:
 https://shared.jovo.to.s3.amazonaws.com/my-file.jpg (making substitutions
 to the URL given in "Web URL")

 Problem: There is no way of overriding the WebURL for HTTPS
 Expected: Cyberduck should use the exact URL given in Web URL and not make
 substitutions, even for https.

--
Ticket URL: <https://trac.cyberduck.io/ticket/9781>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows