[Cyberduck-trac] [Cyberduck] #6040: CDN URL options

Cyberduck trac at trac.cyberduck.ch
Wed Jun 29 21:59:28 CEST 2011

#6040: CDN URL options
 Reporter:  samsen      |         Owner:  dkocher
     Type:  defect      |        Status:  closed
 Priority:  normal      |     Milestone:  4.1
Component:  cloudfiles  |       Version:  4.0.2
 Severity:  normal      |    Resolution:  fixed
 Keywords:              |  Architecture:  Intel
 Platform:  Windows 7   |

Comment (by dkocher):

 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 `CNAME`s 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''

Ticket URL: <http://trac.cyberduck.ch/ticket/6040#comment:12>
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