Cache your CORS

Re:Cache your CORS by icedchai on Tuesday September 20, 2022 @09:33AM (#32911442)

Many devs (young or not, age doesn't matter) simply have no idea how CORS works and don't understand the "same origin" policy. I've seen hundreds of hours wasted on CORS / OPTIONs request implementations that could've been saved with a reverse proxy, if only they knew what one was.

[ Parent | on HN ]

Re:Cache your CORS by LanceH on Tuesday September 20, 2022 @10:37AM (#32912211)

CORS is one of my favorite interview questions (front-end/react dev) as it has the potential to tell me if the interviewee is the person who has researched the problem and implemented solutions. There is a lot of potential discussion from how it works, why it's necessary, to how it is solved in production vs development.

[ Parent | on HN ]

Re:Cache your CORS by javier2 on Tuesday September 20, 2022 @02:22PM (#32915813)

CORS is something I 'fixed' once, five years ago. Hard to talk in detail about that anymore. I wish we would have the time to implement it safely, but alas. We still can't produce an allowList of allowed domains :/

[ Parent | on HN ]

Re:Cache your CORS by LanceH on Thursday September 22, 2022 @06:21PM (#32945384)

> CORS is something I 'fixed' once, five years ago

I'm careful that I don't demand anyone go into depth on any particular subject. CORS is just one opportunity that seems to need a fix with every new project. It also has a variety of solutions, which is again opportunity to show what they know.

There is little point in looking for what a client doesn't know. I've got that covered.

[ Parent | on HN ]