# SSL on Discourse / DO sub-domain of Heroku hosted domain

**URL:** <https://meta.discourse.org/t/ssl-on-discourse-do-sub-domain-of-heroku-hosted-domain/26373>\
**Category:** Self-hosting\
**Created:** [2015年三月15日 20:31 UTC](https://meta.discourse.org/t/ssl-on-discourse-do-sub-domain-of-heroku-hosted-domain/26373 "2015-03-15T20:31:54Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2015年三月15日 20:54 UTC](https://meta.discourse.org/t/ssl-on-discourse-do-sub-domain-of-heroku-hosted-domain/26373/4 "2015-03-15T20:54:41Z")

</div>

I am not following @DKH. Are you basically trying to cut the SSL cost here? You can proxy discourse but there are concerns and complex configurations you need to follow, I would not recommend it.

If you insist see:

> [@Full site CDN acceleration for Discourse](https://meta.discourse.org/t/full-site-cdn-acceleration-for-discourse/21467):
>
> [Fastly](http://www.fastly.com/) , [CloudFlare](https://www.cloudflare.com) and a few other CDNs offer a mode where they accelerate dynamic content. In a nutshell you point your domain IP address at the CDN and the CDN will intelligently decide how to deal with the request. Static content can be easily served from cache Dynamic content can be routed to the site. This provides some advantages over only shipping static assets which is covered in [the CDN howto](https://meta.discourse.org/t/enable-a-cdn-for-your-discourse/14857). You can elect for “[shielding](http://www.fastly.com/products/origin-shield/)” that protects your site from traffic spikes. Dynamic cont…

---

_[View the full topic](https://meta.discourse.org/t/ssl-on-discourse-do-sub-domain-of-heroku-hosted-domain/26373)._