You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
Looks 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?
The text was updated successfully, but these errors were encountered:
204 is no content and is the right behavior for the middleware.chrome should display no content 😊 for this status code. Can you please post your request and response.
Looks 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?
The text was updated successfully, but these errors were encountered: