# Full site CDN acceleration for Discourse

**URL:** https://meta.discourse.org/t/full-site-cdn-acceleration-for-discourse/21467
**Category:** Self-Hosting
**Tags:** cdn, explanation
**Created:** [October 24, 2014, 6:17am UTC](https://meta.discourse.org/t/full-site-cdn-acceleration-for-discourse/21467 "2014-10-24T06:17:57Z")
**Posts on this page:** 1
**Showing post:** 36

<div class="post-metadata">

### Author: ![Hyan](https://avatars.discourse-cdn.com/v4/letter/h/5fc32e/32.png) [@Hyan](https://meta.discourse.org/u/Hyan)
#### Post date: [September 5, 2023, 7:05am UTC](https://meta.discourse.org/t/full-site-cdn-acceleration-for-discourse/21467/36 "2023-09-05T07:05:14Z")

</div>

No, I use the Akamai CDN, which supports cache dynamic content.  
From the first post in this thread, it looks I should set the DISCOURSE\_CDN\_URL as non full site CDN does, though the URL is the same as the website URL. I am just not sure if setting it causes my site broken and other irreversible results, in the end I have to reinstall the software from scratch. In this post [Full Site CDN Using AWS CloudFront](https://meta.discourse.org/t/full-site-cdn-using-aws-cloudfront/208161), the author doesn’t set and leave DISCOURSE\_CDN\_URL unchanged, and it doesn’t require a separate URL to serve message-bus/long-polling. I use this solution and my website is running well so far. The only drawback of the solution is that there’re many relative URL (no base URL, as DISCOURSE\_CDN\_URL value is empty) presenting in the page source, which makes it look not a production level website.

---

_[View the full topic](https://meta.discourse.org/t/full-site-cdn-acceleration-for-discourse/21467)._