I am just writing a quick note here about Rackspace's new CDN product. It looks like it is origin pull and all of that great stuff and built upon Cloud Files somewhat.

  1. http://www.rackspace.com/cloud/cdn-content-delivery-network
  2. http://www.rackspace.com/blog/newsarticles/rackspace-launches-new-conten...
  3. http://docs.rackspace.com/cdn/api/v1.0/cdn-gettingstarted/content/Overvi...

Comments

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented
Issue summary: View changes
Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers as a volunteer commented
Title: New Rackspace CDN Product » Rackspace CDN now uses Origin Pull as well
Component: Origin Pull mode » Documentation
Category: Feature request » Support request

Excellent! And finally :) Origin Pull makes so much more sense than Push 99% of the time.

This means I should just update the README.

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

I am implementing on a test site and I am documenting what I find. There is an issue surrounding the host name being confused. If Akamai receives a CDN request from the origin but the URL is of the root TLD, Akamai will complain and deny the request. So, if "cdn.example.com" is the CDN that Akamai knows about and "www.example.com" makes the request with the usual host_http data, boom, it tells the site to get lost. If we remove the host tag, Akamai is happy.

For reference:

https://www.drupal.org/node/2213429
https://www.drupal.org/node/2499089

I am still digging into this but haven't been able to determine the correct fix for this yet.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers as a volunteer commented

Thanks! Keep us posted :)

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

I just spoke to Akamai again and they said that, at this time, the only way is to remove the host_http tag from the request.

Does anyone have an idea of how to remove/hide it from the request? This appears to be the only stumbling block.

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

I just did a review of the errors being tossed, I think all of the errors are coming from internal pages (authenticated users). Is it possible there is a problem with the authenticated users URL calls are ignoring "cdn.example.com" and making admin page requests? I checked the config and the admin pages are supposed to be ignored.

I wonder if CDN/AdvAgg are getting punked by something wrong with the CDN module?

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

The conversation over on the AdvAgg issue queue.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers as a volunteer commented
Title: Rackspace CDN now uses Origin Pull as well » Rackspace CDN now uses Origin Pull as well: document this
Status: Active » Reviewed & tested by the community
Related issues: +#2213429: FarFuture incompatible with Akamai because of Vary: Accept-Encoding

So the problem described in #3 was a bug in AdvAgg #2213429: FarFuture incompatible with Akamai because of Vary: Accept-Encoding, and was fixed there. That allows us to make this issue as simple as #2 again :)

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

Correct!

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers as a volunteer commented
Status: Reviewed & tested by the community » Fixed

  • Wim Leers committed d8c0986 on 7.x-2.x 
    Issue #2481185 by Wim Leers: Rackspace CDN now uses Origin Pull as well...
opratr’s picture

opratr CreditAttribution: opratr as a volunteer commented

I've setup a sandbox project for a Rackspace CDN module that will use the REST API to purge assets from the CDN cache. It will be similar to the Akamai module functionality. I hope to get started on that ASAP.

https://www.drupal.org/sandbox/sirrion/2513574

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers as a volunteer commented

#12: You don't need that if you're using the CDN module's Far Future expiration feature.

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

Correct. I confirmed with one of the CDN product managers that there are some changes coming to the Edge Rules and a full purge option (right now, from the control panel, you can purge individual files).

opratr’s picture

opratr CreditAttribution: opratr as a volunteer commented

Sorry, I probably shouldn't have posted that comment in this thread, necessarily. In the context of how the CDN module functions (i.e. dealing with static content resources like images, CSS, etc.) a Rackspace CDN module wouldn't make sense and would be totally unnecessary.

However, in instances where you have your entire site behind the origin-pull Rackspace CDN, including page content, files, etc., there are definitely valid use cases for purging content from the CDN network as it gets updated, deleted, etc. I know the sites I've built using the Akamai CDN would not have worked without the Akamai module.

Sorry for the confusion.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers as a volunteer commented

However, in instances where you have your entire site behind the origin-pull Rackspace CDN, including page content, files, etc., there are definitely valid use cases for purging content from the CDN network as it gets updated, deleted, etc. I know the sites I've built using the Akamai CDN would not have worked without the Akamai module.

Oh, yes, absolutely! Assets only vs. entire site is indeed a hugely important distinction.

You may want to look at https://www.drupal.org/project/purge then btw.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.