I see a lot of confusion and frustration (on Stack Overflow and other places) when implementing CORS. Part of this is because the browser doesn't give any useful information when there is a CORS error. I'd like to write a guide discussing various techniques for debugging CORS errors.
@monsur what are the techniques? We are starting to update some of the contentn strategy and I think this would be a good article. I am just trying to work out how long it would be and where it would fit in with the existing articles.
Please do! I would love to learn, trying to debug CORS now and it's so painful.
@monsur are you still up for this
Thanks for the update. I will open it up to other developers to take on in the new year. Currently looking at how we can radically change the contribution model.