I added the following statements in our app.yml DISCOURSE_ENABLE_CORS: true DISCOURSE_CORS_ORIGIN: '*' Temporarily set ‘*’ to eliminate variables while testing. I have also attempted setting urls explicitly to no avail. However, despite the above, we still get Blockquote No ‘Access-Contro…

cors origins setting is controlled in admin > settings > security you only need DISCOURSE_ENABLE_CORS: in your app.yml

I attempted and tested this as well [image]

And for our single site setup setting origin in .yml vs. the admin ui should have the same effect per: What is the purpose of Settings -> Security -> CORS origins vs similar environment setting?

I’m not sure we support the wildcard here. Can you try it with a real domain? We are using the cors settings in a couple sites with domains configured and it appears to work fine.

i also have it set on one of my sites and it does work

I attempted with a domain, no luck. Is there a way to confirm that the env vars are set correctly? (or that the app restart configured the cors without resending requests, just trying to think of ways to debug). I think this is the part of code that handles the cors settings, just in case it is use…

[image] Within the ngnix access logs I notice that the OPTIONS call returns a 404 (and precedes the error on the GET call)

DISCOURSE_ENABLE_CORS: true로 설정했는데도 'Access-Control-Allow-Origin' 헤더가 없습니다

지원

xprmnts 10월 28, 2021, 1:53오후 3

저도 시도해 보고 테스트해 보았습니다

글		댓글	조회수
What is the purpose of Settings -> Security -> CORS origins vs similar environment setting? Support	2	3744	11월 9, 2015
CORS origins setup does not work Support	6	2085	10월 22, 2020
Set DISCOURSE_ENABLE_CORS for hosted forum Self-hosting hosting	5	2609	10월 7, 2022
Multiple cors origins on hosted discourse? Support	8	3196	8월 21, 2017
CORS issue with javascript frontend Self-hosting	1	732	7월 20, 2020

DISCOURSE_ENABLE_CORS: true로 설정했는데도 'Access-Control-Allow-Origin' 헤더가 없습니다

Related topics