-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORS issue on chrome #5
Comments
Hi👋, I could not reproduce it on my end. The following config is required for both latest cors({
credentials: true,
origin: /localhost.*/
}) Here is described why: Maybe a server was not restarted during your development or a browser cached something. If you keep having problems with this please send a code snipped to reproduce it. |
Bumping this issue as I'm getting the same issues as OP. My experience:
If you're using Postman, try removing the 'Host' key in the header and that's the issue AFAIK |
Bumping this issue as I'm also getting the same issues. My experience: Tested on both Chrome and Brave with cache disabled. |
When using fetch with credentials to make a request to a separated backend (other url/port), everything works perfectly with Firefox with default configuration (
use(cors())
)On Chrome, it seems we need to specify all the default options for it to works:
Any ideas what is causing this?
The text was updated successfully, but these errors were encountered: