{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/CORS/issues/19","labels_url":"https://api.github.com/repos/aspnet/CORS/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/CORS/issues/19/comments","events_url":"https://api.github.com/repos/aspnet/CORS/issues/19/events","html_url":"https://github.com/aspnet/CORS/issues/19","id":75665103,"number":19,"title":"Chrome treats any non-200 responses to preflight requests as a failure","user":{"login":"danroth27","id":1874516,"avatar_url":"https://avatars.githubusercontent.com/u/1874516?v=3","gravatar_id":"","url":"https://api.github.com/users/danroth27","html_url":"https://github.com/danroth27","followers_url":"https://api.github.com/users/danroth27/followers","following_url":"https://api.github.com/users/danroth27/following{/other_user}","gists_url":"https://api.github.com/users/danroth27/gists{/gist_id}","starred_url":"https://api.github.com/users/danroth27/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danroth27/subscriptions","organizations_url":"https://api.github.com/users/danroth27/orgs","repos_url":"https://api.github.com/users/danroth27/repos","events_url":"https://api.github.com/users/danroth27/events{/privacy}","received_events_url":"https://api.github.com/users/danroth27/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-12T16:44:00Z","updated_at":"2015-05-12T16:44:00Z","closed_at":null,"body":"From @sandorfr (originally filed as aspnet/mvc#2542)\r\n\r\nLooks like the current implementation of cors return a 204 for preflight request and it looks like Chrome considers any non-200 being a failure. Doing some quick research on the web I've seen that there is discussions about what should be the good behavior but what I'm sure of is that we need that to just work. Maybe we should be able to configure it?"}}