[Cyberduck-trac] [Cyberduck] #6570: https protocol should default to port 443 if no port is specified

Cyberduck trac at trac.cyberduck.ch
Thu Mar 22 04:39:36 CET 2012

#6570: https protocol should default to port 443 if no port is specified
 Reporter:  liemmn     |         Owner:  dkocher
     Type:  defect     |        Status:  new
 Priority:  normal     |     Milestone:  4.3
Component:  openstack  |       Version:  4.2.1
 Severity:  normal     |    Resolution:
 Keywords:             |  Architecture:
 Platform:             |

Comment (by liemmn):

 I tried it with the latest snapshot build (9485) version 4.2.1 with same
 results.  Steps to reproduce:

 1) Install Swift (running on HTTPS, port 443)
 2) Install Keystone, be sure to set the Swift endpoint to point to your
 Swift instance with HTTPS protocol and do not specify the port number, so
 the URL should be something like https://<swift_proxy>/v1.0/%tenant_id%.
 3) Point Cyberduck to authenticate with your Keystone instance via port
 35357 (using the Cyberduck's Swift connector)
 4) Capture the HTTP traffic with a proxy like Burp or Paros so you can see
 the requests and responses.
 5) You will see that Keystone responses the authentication request with an
 X-Storage-Url: https://<swift_proxy>/v1.0/<tenant_id>
 6) Cyberduck then makes a GET to Swift proxy on port 35357! (should be
 using 443)
 7) At this point, if you modify the request to use port 443, then the
 Swift GET will succeed, else it will fail.

 It appears that Cyberduck tries to use the port of the auth host, if a
 port from the X-Storage-Url is not specified, even if the protocol is

 Please let me know if you need help reproducing this....  Thanks.

Ticket URL: <http://trac.cyberduck.ch/ticket/6570#comment:3>
Cyberduck <http://cyberduck.ch>
Open source FTP, SFTP, WebDAV, Cloud Files, Google Docs & Amazon S3 Browser for Mac & Windows.

More information about the Cyberduck-trac mailing list