Skip to content
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.

Guide to debugging CORS requests #282

Closed
monsur opened this issue Jan 29, 2013 · 5 comments
Closed

Guide to debugging CORS requests #282

monsur opened this issue Jan 29, 2013 · 5 comments

Comments

@monsur
Copy link
Contributor

monsur commented Jan 29, 2013

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.

@PaulKinlan
Copy link
Member

@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.

@kevinmtrowbridge
Copy link

Please do! I would love to learn, trying to debug CORS now and it's so painful.

@PaulKinlan
Copy link
Member

@monsur are you still up for this

@monsur
Copy link
Contributor Author

monsur commented Dec 13, 2013

Hi Paul. Unfortunately I don't have the time to do this. Thanks!

On Wed Dec 11 2013 at 11:59:31 PM, Paul Kinlan notifications@github.com
wrote:

@monsur https://github.com/monsur are you still up for this


Reply to this email directly or view it on GitHubhttps://github.com//issues/282#issuecomment-30391340
.

@PaulKinlan
Copy link
Member

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants