I appreciate the article, but you do make one mistake I see in such articles across the web. That is you quietly mix the roles and client and server in your presentation.
You start with "Most of browsers do not allow CORS" and then list three server solutions ...
It is precisely this that trips us up with CORS from the get go. What role the browser plays and what role the server plays. It's worth some effort to differentiate these clearly.
Thank you for the feedback! To be honest, the concept is still not perfectly crystal clear for me, and that's why I needed to summarize it. It got a little more clearer thanks to your comment:)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I appreciate the article, but you do make one mistake I see in such articles across the web. That is you quietly mix the roles and client and server in your presentation.
You start with "Most of browsers do not allow CORS" and then list three server solutions ...
It is precisely this that trips us up with CORS from the get go. What role the browser plays and what role the server plays. It's worth some effort to differentiate these clearly.
Thank you for the feedback! To be honest, the concept is still not perfectly crystal clear for me, and that's why I needed to summarize it. It got a little more clearer thanks to your comment:)