-
Notifications
You must be signed in to change notification settings - Fork 5k
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
HttpProvider: CORS issue with Firefox and Safari #3112
Conversation
Added the in-progress label again because it can't find the global |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM - it works in 2.x with no problems?
It would be cool to try to reproduce the CORS error (at least for Firefox) in headless browser testing but those fixtures need to be built.
What about docs changes for the new option?
@cgewecke Yeah, it's really strange and couldn’t clearly figure out why the process global var isn't existing in nodejs v12 for these tests.
I wrote it down on my todo list and will mention it on the missing comment to your e2e issue.
Providers weren’t documented until now. I wrote that down on the todo list as well and will create a related issue for it today. I will merge this PR for now. |
* CORS error fixed
Fixes #2978 and adds the options property
withCredentials
.