So, there is a way to allow JS API requests from domains other than where you Discourse is hosted. For example, you’d like to embed a topic list that is a result of search by some criteria - and you want to do it with JavaScript only, making it call your Discourse’s API. For this to work, you’ll n…

See here: [YSY] Why is the same origin policy so important? web-application, web-browser, javascript, same-origin-policy asked by YSY on 10:34PM - 19 Oct 11 UTC Bottom line, it is a very bad idea to enable *

In general, is still bad for enabling a single domain only?

So, the only really safe way to query API from a different domain would be to allow JSONP: either by origin domain or by api_username/key, right? If that’s correct, I’ve seen some discussion about JSONP in this topic - have it been considered for implementation eventually?

What are the risks of enabling Cross-origin resource sharing (DISCOURSE_ENABLE_CORS)

Product Support

sam (Sam Saffron) 3월 18, 2016, 3:25오전 4

Allowing sites you do not control CORS access is a bad idea.

글		댓글	조회수
Setup Cross-Origin Resource Sharing (CORS) Self-Hosting how-to	8	2281	1월 13, 2026
What is the purpose of Settings -> Security -> CORS origins vs similar environment setting? Product Support	2	3752	11월 9, 2015
CORS issue with javascript frontend Self-hosting	1	739	7월 20, 2020
Set DISCOURSE_ENABLE_CORS for hosted forum Self-hosting hosting	5	2620	10월 7, 2022
Where I should go to set the `DISCOURSE_ENABLE_CORS` env variable? Product Support	16	1352	12월 27, 2022

What are the risks of enabling Cross-origin resource sharing (DISCOURSE_ENABLE_CORS)

Related topics