cdn

Merhaba,
cdn eklentisini alt alan adları ile kullanmak istiyorum.
Örneğin js.alan.com css.alan.com şeklinde alt alan adlarından dosyaları servis etmek istiyorum. Bunun için bayağı bir google araması yaptım fakat nasıl yapılacağını bulamadım.(belkide buldum ama ben anlamadım, bilemiyorum)
sıkıntı bu, umarım yeterince açık olmuştur.

Hi,

I use a CDN module for the parallel request.
But it creates a SEO problem. Same article can me available from many sub-domains:

mysite.com/article
cdn1.mysite.com/article
cdn2.mysite.com/article
cdn3.mysite.com/article

I am working on a site, which will eventually use both varnish and a CDN and I am going to implement both of these solutions.

What I am unsure about is which one first. The server at the moment can handle the load that it is getting, so my thoughts are which will get the page into the hands of the user quickest.

I am sure that this could be argued either way, but do people have guidelines or weighing factors as to which way round these should be implemented.

All I'm really seeing online are reviews by affiliates, so I thought I'd ask for more unbiased opinions.

Any of you had any experience using CloudCache's CDN? I was sent a coupon and it would be very cost effective for me to use them, but I'm not sure if the service is good.

I have heard many experts state that the use of a CDN has no impact on SEO, but I am not convinced. Clearly speeding up a website WILL have a positive impact but my primary area of concern is with regard to PageRank.

My understanding of pagerank is that it is calculated on a per domain basis and that each sub-domain is considered a separate domain.

If you have multiple webnodes , you need some kind of shared filesystem to sync uploaded files, static files etc.

Instead, what if you use a pull based CDN system. So all your files can be served from cdn1.yourdomain.com and all webnodes point to CDN.
the benefits are
1) You don't need to worry about managing a shared file system
2) You also get a free frontend to server static files.

This looks like a much tempting option than shared file system. Do you agree? Or there are gotchas I am not thinking through?

In our stable of D6/PF6 publishing sites, several have these qualities in common:

• Delivered by Akamai.
• /admin and other sensitive paths are locked out of the public site (example.com/admin) and available only on our internal network (e.g., internal.example.com/admin).
• Cookies are shared on the domain level (.example.com).
• admin_menu enabled.
• Akamai is set to ignore the app's cache-control headers in certain places, or across the whole site.

We have a high traffic site hosted on a VPS and we are trying to offload the image, CSS and JS file requests to a CDN. We are considering using Amazon S3 and the Media Mover module to send all files to Amazon (using this approach http://www.24b6.net/2009/10/04/simple-cdn-media-mover-and-s3).

Does anyone have experience setting this up or suggestions on other approaches?

I have a project coming up with a significant media serving component. I'm looking to have a talk with people who have experience integrating a Drupal site with a CDN (Akamai, Amazon, whatever). I'm particularly interested in how you can restrict CDN access to authorized Drupal users only. I'd be happy to buy you lunch for an hour's conversation.

Hi,

I am considering all my media content to webair CDN
http://www.webair.com/pdf/WebairCDN_SecureURLs.pdf

Will I be able to maintain access control to media for members/non-members with http://drupal.org/project/cdn and is there anyone out there that can set this up for me ?

Regards Allan