CDN URL options

[cyberduck]

a998853 created the issue

Quite often we need to email a link to a file on RackSpace CloudFiles, that's in a CloudFiles container. Since these could be large video files, giving them a link is the fastest most efficient thing to do.

However:

1. Under windows, CopyURL doesn't copy the URL to the clipboard so that it can be pasted.

2. And if it does, it should be the external URL that is copied, and preferably the the CNAMEd URL if it exists.

Currently the only option is to download file, because there is no way to highlight and copy the link, even though we can see it on the screen. So we have to resort to using FireUploader for that single function.

So would be good if:
A. The Copy URL worked

B. And like it is in FireUploader, change the type of the control that any URLs are displayed in, in the Info Pop-up, can be highlighted with the dragging of the mouse pointer, and then copying to the clipboard with C. This would allow the user to pick the URL they want to copy.

C. If it it possible, show any CNAMEd URLs to the file, by reading the DNS system, using the new RackSpace API for that purpose.

---

Attachments

• CyberDuck1CopyURLdoesntLoadClipboard.png (92.9 KiB)
• CyberDuck2OpenURLrequiresDownloadofLargeFiles.png (93.5 KiB)
• CyberDuck3InfoCantGrabURL.png (93.6 KiB)
• CyberDuck4ResortToUsingFireUploaderToGetURL.png (104.4 KiB)

[cyberduck]

@dkocher commented

Replying to [6040 samsen]:

1. Under windows, CopyURL doesn't copy the URL to the clipboard so that it can be pasted.

The CDN (Akamai) URL is unknown until after you have selected File → Info for any file in a given CDN enabled container. We currently do not preload CDN container information.

[cyberduck]

@dkocher commented

Replying to [6040 samsen]:

2. And if it does, it should be the external URL that is copied, and preferably the the CNAMEd URL if it exists.

The CNAME is not known as for Rackspace this is only managed in the DNS itself but is not part of the management API.

[cyberduck]

@dkocher commented

In afe9889.

[cyberduck]

a998853 commented

"The CDN (Akamai) URL is unknown until after you have selected File → Info for any file in a given CDN enabled container. We currently do not preload CDN container information."

But the OpenURL works as you see in my screen shots, so you must have the URL... the issue described is the that URL is NOT copied to the clipboard. And no mention is made whether this has been fixed or not.

And no mention has been made whether the URL(s) can be cut an pasted from the FileInfo pop-up, so it's not 'clear' what has been 'fixed'.

"The CNAME is not known as for Rackspace this is only managed in the DNS itself but is not part of the management API."

Yes, I should have broken this into TWO tickets, one was a defect, and another was an enhancement request/suggestion. The point about CNAMEs, is that you do have the account name and API key, so you have access to the DNS via their new API, using those two values. A query in the DNS for any URL that matches the CDN URL you show in FileInfo, would return any CNAMES that have been assigned to it. You would only need to implement it FileInfo, as there it would be a simple single file lookup (that could return 0 or more entries, though most often it would be 0 or 1 results).

[cyberduck]

@dkocher commented

Replying to [comment:4 samsen]:

"The CDN (Akamai) URL is unknown until after you have selected File → Info for any file in a given CDN enabled container. We currently do not preload CDN container information."

But the OpenURL works as you see in my screen shots, so you must have the URL... the issue described is the that URL is NOT copied to the clipboard. And no mention is made whether this has been fixed or not.

Please update to the latest snapshot build available. Using the latest build should list the CDN URL in the Edit → Copy URL menu.

[cyberduck]

@dkocher commented

Replying to [comment:4 samsen]:

A query in the DNS for any URL that matches the CDN URL you show in FileInfo, would return any CNAMES that have been assigned to it. You would only need to implement it FileInfo, as there it would be a simple single file lookup (that could return 0 or more entries, though most often it would be 0 or 1 results).

From what I know DNS does not support such queries.

[cyberduck]

@dkocher commented

Replying to [comment:4 samsen]:

And no mention has been made whether the URL(s) can be cut an pasted from the FileInfo pop-up, so it's not 'clear' what has been 'fixed'.

In File → Info it should be possible to right-click on the URL to copy it to the clipboard.

[cyberduck]

a998853 commented

"From what I know DNS does not support such queries."

Again, RackSpaceCloud has very recently released an API, that with the AccountName, and APIkey will return a complete list of CNAMEs from the DNS, and probably a short list of CNAMEs related to a given base CDN URL.
http://www.rackspace.com/cloud/blog/2011/03/21/announcing-rackspace-cloud-dns-api-private-beta-for-us-uk-cloud-customers/
Your Users have Given your application that same AccountName, and APIkey to be able to connect to their cloudfiles site.

[cyberduck]

@dkocher commented

Replying to [comment:8 samsen]:

"From what I know DNS does not support such queries."

Again, RackSpaceCloud has very recently released an API, that with the AccountName, and APIkey will return a complete list of CNAMEs from the DNS, and probably a short list of CNAMEs related to a given base CDN URL.
http://www.rackspace.com/cloud/blog/2011/03/21/announcing-rackspace-cloud-dns-api-private-beta-for-us-uk-cloud-customers/
Your Users have Given your application that same AccountName, and APIkey to be able to connect to their cloudfiles site.

The problem with this approach is that the solution will only work for the percentile of users that actually manage DNS with Rackspace.

[cyberduck]

a998853 commented

Replying to [comment:9 dkocher]:

Replying to [comment:8 samsen]:

"From what I know DNS does not support such queries."

Again, RackSpaceCloud has very recently released an API, that with the AccountName, and APIkey will return a complete list of CNAMEs from the DNS, and probably a short list of CNAMEs related to a given base CDN URL.
http://www.rackspace.com/cloud/blog/2011/03/21/announcing-rackspace-cloud-dns-api-private-beta-for-us-uk-cloud-customers/
Your Users have Given your application that same AccountName, and APIkey to be able to connect to their cloudfiles site.

The problem with this approach is that the solution will only work for the percentile of users that actually manage DNS with Rackspace.
Good point. We noticed (probably on spec) that you opened up a field on the Info Tab of your latest snapshot. Sorry about being a 'noob' again, but without using an API, how else can you automatically find the CNAME for a CDN URL? Is there a more generic way of doing it? I thought that the purpose of a CNAME is to hide CDN URL, and it's not clear to me how one can go in reverse to find the CNAME without an API provided by Hosting Provider. While using external CNAME services is possible, doesn't that double the bandwidth charges? And if so, I pretty sure that in most cases someone using RackSpace to host their CDN content, would use the DNS services in their account also. Again, I may not have a clue how things work, but this seems logical to me.

[cyberduck]

@dkocher commented

Replying to [comment:10 samsen]:

Good point. We noticed (probably on spec) that you opened up a field on the Info Tab of your latest snapshot. Sorry about being a 'noob' again, but without using an API, how else can you automatically find the CNAME for a CDN URL? Is there a more generic way of doing it? I thought that the purpose of a CNAME is to hide CDN URL, and it's not clear to me how one can go in reverse to find the CNAME without an API provided by Hosting Provider. While using external CNAME services is possible, doesn't that double the bandwidth charges? And if so, I pretty sure that in most cases someone using RackSpace to host their CDN content, would use the DNS services in their account also. Again, I may not have a clue how things work, but this seems logical to me.

It doesn't matter what DNS provider you use to point a CNAME to the CDN. And I guess the majority won't even bother about the DNS solutions offered by Rackspace (in beta) if an existing infrastructure already exists.

This is different to Amazon CloudFront, where you are required to provide the CNAMEs you configure in the DNS to CloudFront (using the API). CloudFront only answers HTTP requests with a Host header that match these. Therefore there is an input field to in the Info → CDN window.

[cyberduck]

@ylangisc commented

Copy URL as context menu command available as of c66cc76.