# Multiple cors origins on hosted discourse?

**URL:** <https://meta.discourse.org/t/multiple-cors-origins-on-hosted-discourse/68172>\
**Category:** Product Support\
**Created:** [August 16, 2017, 6:26pm UTC](https://meta.discourse.org/t/multiple-cors-origins-on-hosted-discourse/68172 "2017-08-16T18:26:59Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [August 21, 2017, 12:49pm UTC](https://meta.discourse.org/t/multiple-cors-origins-on-hosted-discourse/68172/13 "2017-08-21T12:49:45Z")

</div>

Note, the error was actually nothing to do with the CORS origins, instead it was a particular HTML structure our “except parser” exploded on. If you had empty content in certain nodes we were totally unable to generate excerpts, something that broke topic creation.

---

_[View the full topic](https://meta.discourse.org/t/multiple-cors-origins-on-hosted-discourse/68172)._