-
-
Notifications
You must be signed in to change notification settings - Fork 299
CDN URL options #6040
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Replying to [6040 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. |
Replying to [6040 samsen]:
The |
"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). |
Replying to [comment:4 samsen]:
Please update to the latest snapshot build available. Using the latest build should list the CDN URL in the Edit → Copy URL menu. |
Replying to [comment:4 samsen]:
From what I know DNS does not support such queries. |
Replying to [comment:4 samsen]:
In File → Info it should be possible to right-click on the URL to copy it to the clipboard. |
"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. |
Replying to [comment:8 samsen]:
The problem with this approach is that the solution will only work for the percentile of users that actually manage DNS with Rackspace. |
Replying to [comment:9 dkocher]:
|
Replying to [comment:10 samsen]:
It doesn't matter what DNS provider you use to point a This is different to Amazon CloudFront, where you are required to provide the |
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:
Under windows, CopyURL doesn't copy the URL to the clipboard so that it can be pasted.
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)The text was updated successfully, but these errors were encountered: