You just link to a basic example that uses CORS at some point, then a link to the MDN docs on CORS. If by educational, you mean I get to read that, then I guess?
I far prefer OP's article here, since it walks through why the various CORS headers are needed, and the results of each stage.
I don't get why you think you're being "piled up on". You started by insulting the article on Twitter, then linking that tweet here, effectively insulting it again.
You aren't the victim, you're being called out for being a jerk.
My advice is to look closely at what you did, apologize and do better going forward.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
my follow up is here:
know thy CORS, glitch & fetch! :)
dataPixy ・ Nov 17 ・ 1 min read
You should really just follow the links ...
I hope you'll find it handy and educational too ;)
You just link to a basic example that uses CORS at some point, then a link to the MDN docs on CORS. If by educational, you mean I get to read that, then I guess?
I far prefer OP's article here, since it walks through why the various CORS headers are needed, and the results of each stage.
No need to be a jerk about it.
I don't get why you think you're being "piled up on". You started by insulting the article on Twitter, then linking that tweet here, effectively insulting it again.
You aren't the victim, you're being called out for being a jerk.
My advice is to look closely at what you did, apologize and do better going forward.
Kevin, go write your ideal post on CORS. You could use 1 :)