Cloud Platform CDN
This documentation page describes features and procedures for a beta
product, and its contents may change at any time. Acquia does not
recommend bookmarking this page as its location may change without notice.
This feature is available only for eligible Cloud Platform Enterprise
subscribers. For more information, contact your Account Manager.
Using the Cloud Platform CDN, you can deliver accelerated digital
experiences to global audiences by caching pages and static assets (including
JavaScript, CSS, and images) at over 65 points of presence (POPs) around the
world. Visitors accessing your website will load the static assets from the
POP closest to their location, which decreases the amount of time required to
load a page, and can lead to increased conversions.
Acquia configures and manages the Cloud Platform CDN so you don’t have
to. Based on years of experience accelerating Drupal applications
through Varnish®, Acquia has
configured the Cloud Platform CDN to optimize the delivery of digital
experiences built with Drupal.
Maintaining cache consistency
The Cloud Platform CDN fully respects both HTTP Cache-Control
headers and tag-based
invalidation, which was first introduced in Drupal 8. Acquia recommends
continuing to use both methods as part of your application’s caching strategy.
Troubleshooting
Cloud Platform CDN may not provision for any of the following reasons:
No domains registered to environment (except acquia-sites.com):
The default *.acquia-sites.com domain cannot be added to the CDN. You must add
at least one of your own domains before Platform CDN can be provisioned.
Your domain was previously registered with Acquia’s CDN partner, Fastly Inc.:
If you or your agency created a Fastly account in the past using one of your
domain names then contact Acquia support.
Acquia support will work with Fastly to free up the domain for use on Platform
CDN.
Old certificate is being served instead of the newly uploaded certificate:
This can happen if your new certificate has a wildcard domain and the old
certificate has a different wild card or an exact match. Platform CDN will
serve a valid certificate with the most-matching CN or SAN. De-active the old
certificate via Acquia Cloud UI or contact Acquia support for assistance.
HTTP to HTTPS redirect gets stuck in a 301 redirect loop:
Purge all caches. If the problem persists please contact Acquia support.
SSO redirects browser to not-logged-in content:
Ensure your application is serving a Cache-Control header with value max-age:3
or must-revalidate so that the browser does not use its local cache.
Purge token lost or doesn’t work:
A lost token can be recovered. See Purging the Platform CDN cache.
If your token doesn’t allow purging objects from Platform CDN,
contact Acquia support.
The acquia-purge module is not working correctly:
Use Drush 9 to run drush p:dia.
If that command is not available, use the following method to ensure that all
the modules are installed and enabled:
# in your local dev environment
git clone [email protected]:manualtest.git
cd manualtest/docroot
# Use composer to install acquia_purge 1.1 beta and its dependencies
composer config minimum-stability 'beta'
composer config prefer-stable true
composer require 'drupal/acquia_purge:1.1-beta1'
# Push the code back and enable the module using drush
git add.
git commit -a -m "Add Acquia Purge module"
git push
ssh {{YOUR SSH URI HERE}}
sudo su
cd /var/www/html/{{YOUR ENVIRONMENT NAME HERE}}/docroot/
source /mnt/users/[SITEGROUP NAME]/dev.shell
drush9 en acquia_purge
yes
#>> [success] Successfully enabled: acquia_purge, purge, purge_drush
# list all the available purgers
drush9 p:purger-lsa
#>> --------------------- ---------------------------- ----------------------------------------------
#>> Plugin Label Description
#>> --------------------- ---------------------------- ----------------------------------------------
#>> acquia_purge Acquia Cloud Invalidate content from Acquia Cloud.
#>> acquia_platform_cdn Acquia Platform CDN (beta) Invalidate content from Acquia Platform CDN.
#>> --------------------- ---------------------------- ----------------------------------------------
# Enable the acquia purge and then the acquia_platform_cdn in that order to ensure
# varnish clears first and then platform_cdn clears after a short delay
drush9 p:purger-add acquia_purge
drush9 p:purger-add acquia_platform_cdn
# Enable the other purge modules that need manually enabled for some reason
drush9 pm:list | grep purge
drush9 en purge_processor_cron
drush9 en purge_processor_lateruntime
drush9 en purge_queuer_coretags
drush9 en purge_tokens
drush9 en purge_ui
drush9 en purge_drush
drush9 pm:list | grep purge
# Run the diagnostic
drush9 p:dia
