CDN for Drupal
Let Drupal render. Let the edge repeat.
Drupal sites often combine large files directories with anonymous page caches that still get requested from a single origin. Global audiences turn every CSS, JS and public-node request into origin work.
Cache theme assets, the files directory and eligible anonymous pages at Cloud CDN. Bypass authenticated Drupal routes and forms. Purge when editorial content is published.
Why teams use Aptranet
What CDN for Drupal looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Anonymous pages closer to readers
Public nodes, views and landing pages are served from 210+ locations with 30 ms average latency.
Files directory off the origin
Images, documents and generated styles are cached and can be transformed at the edge.
Editors still hit Drupal
Logged-in editorial, preview and form POSTs bypass cache so Drupal remains the source of truth.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Connect the Drupal origin
Pull the existing Drupal host over HTTPS, including /sites/*/files and theme asset paths.
- 2Cache anonymous GETs
Honour Drupal cache headers or set CDN TTLs for public pages. Bypass session cookies used by authenticated users.
- 3Hook purge to publish
Purge node URLs and files when content is published or media is replaced.
- 4Map the public hostname
Attach the production domain and certificate after validating on an Aptranet hostname.
Outcomes
What changes once the hostname is on Aptranet.
- Public Drupal pages are cached at the edge
- Authenticated editorial traffic stays dynamic
- The files directory is delivered globally
- Publish events can purge the affected URLs
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Use purge on publish for the URLs that changed. Cache-tag-to-URL mapping remains an origin concern; the CDN invalidates by URL, file or directory.
Only if the HTML is truly shareable. Most Drupal authenticated responses should bypass cache.
Keep private file routes on the origin. Cache the public files directory only.
Yes for catalogue, media and anonymous pages. Keep cart and checkout dynamic, as with other commerce platforms.