Why we need to know about CORS (2020)
evan-moon.github.io
Why we need to know about CORS (2020)
1–9 of 9 posts
Re: Why we need to know about CORS (2020)
#2[dead]
Re: Why we need to know about CORS (2020)
#3[dead]
this is also a standard approach for nginx:
location / {
if ($http_origin ~ "^https?://(www\.)?doma.in$") {
add_http_header Access-Control-Allow-Origin "$http_origin";
}
}Re: Why we need to know about CORS (2020)
#4(2020)
Re: Why we need to know about CORS (2020)
#5The lack of word wrapping, that we have grown so accustomed to on the Web, makes this article nearly illegible.
Re: Why we need to know about CORS (2020)
#6The lack of word wrapping, that we have grown so accustomed to on the Web, makes this article nearly illegible.
Fixed! Thanks for the heads-up. I'm used to writing in Korean where wrapping is rarely an issue, so I missed this during the English migration. It's updated now—thanks for the patience!
Re: Why we need to know about CORS (2020)
#7I’m dealing with this now actually. So good timing.
Re: Why we need to know about CORS (2020)
#8I'm guessing in 2026, your favorite LLM and it just gives you the answer
Re: Why we need to know about CORS (2020)
#9I'm guessing in 2026, your favorite LLM and it just gives you the answer
True, LLMs are great at giving immediate fixes. My goal with this post was to provide the 'why' and the underlying structure that helps you debug it even when the LLM gives you a hallucinated config :)