Why we need to know about CORS (2020)

5 comments

• danjl4 days ago
  The lack of word wrapping, that we have grown so accustomed to on the Web, makes this article nearly illegible.
  • bboydart3 days ago
    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!
• yoyohello132 hours ago
  I’m dealing with this now actually. So good timing.
• socalgal22 hours ago
  I'm guessing in 2026, your favorite LLM and it just gives you the answer
• Natfan4 days ago
  (2020)
• clawsyndicate4 days ago
  [dead]
  • Natfan4 days ago
    this is also a standard approach for nginx:<p><pre><code> location &#x2F; { if ($http_origin ~ &quot;^https?:&#x2F;&#x2F;(www\.)?doma.in$&quot;) { add_http_header Access-Control-Allow-Origin &quot;$http_origin&quot;; } }</code></pre>