[Cyberduck-trac] [Cyberduck] #7676: Openstack Swift Temporary URL Links should contain HTTP Port (as well)

[Cyberduck]

#7676: Openstack Swift Temporary URL Links should contain HTTP Port (as well)
--------------------------------------------+------------------------
 Reporter:  sschlott                        |         Owner:  dkocher
     Type:  enhancement                     |        Status:  closed
 Priority:  normal                          |     Milestone:  4.5
Component:  openstack                       |       Version:  4.4.3
 Severity:  normal                          |    Resolution:  fixed
 Keywords:  Openstack Swift, Temporary URL  |  Architecture:
 Platform:                                  |
--------------------------------------------+------------------------

Comment (by sschlott):

 Hi, I had just had a look at the snapshot build 14153, which should
 contains the changes mentioned above, I guess.

 It seems as if there was a slight misunderstanding regarding what was
 meant with showing the right port. The intention was not to show the same
 links for HTTP as well as HTTPS. At our deployment Swift listens with
 HTTPS but not at 443. The intention was to recognize the non-standard port
 (e.g. 8080 or 8888) as given in the Openstack Keystone catalog.

 I try to make the underlying problem more clear:
 An Openstack deployer might want to provide different services (e.g. API
 endpoints) listening on different ports at the very same IP address. A
 deployment might look like this:

 keystone.deployment.de (DNS A Record --> IP1)

 object.deployment.de (DNS A Record --> IP1) --> Openstack Swift

 with the following service endpoints:

 https://keystone.deployment.de:5000/v2.0

 https://object.deployment.de:8080/v1/AUTH_


 E.g. we have one deployment where the Swift Endpoint is reachable through
 port 8080 but with HTTPS. In the context menu 'Copy URL' the 'HTTPS URL'
 is right - it shows https://DNS-NAME:8080/v1. The links for the Temporary
 URL should also contain port 8080 and HTTPS, because that is the location
 where Swift listens and which is correctly provided by the Keystone
 service catalog.

 The reason for the ticket was that the Temporary URLs did not point to the
 Swift endpoint correctly (because of the missing port). Also, the port
 could be 1234, 8888 or every other valid port not already used. It just
 has to match the content of the Keystone service catalog entry describing
 Swift's public URL of this deployment.

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