-
Notifications
You must be signed in to change notification settings - Fork 5.1k
'request.withCredentials = true' breaks CORS #1802
Comments
I am also experiencing this after migrating to version 35, following. |
i can confirm this, after downgrading to 0.20.6 it worked again. |
Related to #1803 |
Encountered the same issue which says 'The value of the 'Access-Control-Allow-Credentials must be true'. I'm using [email protected] |
after downgrading to 0.20.6 it worked again. It works as well |
i found safari will add |
@tradzero downgrade to v1.0.0-beta.33 solved my problem |
For users of v1.0.0-beta, downgrading to v1.0.0-beta.34 will also work, because the issue was introduced after it, in this commit. I had to downgrade in order to use HttpProvider with Infura. Probably the longer-term solution is to allow |
see my comment on web3/web3.js#1802
I can confirm that downgrading to v1.0.0-beta.34 fixes the issue. Both Safari and Firefox were impacted. |
What is the correct command to downgrade to that specific version? |
@karlphillip something like |
Thank you, ended up going with: |
Any ideas on how to solve this - I find it works in most browsers but safari? |
I have the same issue and can not resolve with Chrome, FireFox and Safari... |
Im getting this error also :( |
This got fixed with PR #2564 and will be released this week. |
Thank you so much. It saved my day. |
I think I'm seeing the same issue on a MAC build of Clickz Latest, which is trying to run the following dat://795f83fa1356cd7d00e5cfe8f1a93f32c55127684c6fc4cb8ff89a32e000016b That is a frontend to some contracts running on the Ethereum Rinkeby Test Network, so it relies on MetaMask to inject a web3.js instance that points to Rinkeby. Unfortunately, no matter what I do with MetaMask, my app' thinks it's on the Ropsten network, and I get these errors:
I'm assuming that the reference to Interestingly, the very same Meanwhile, what to do concerning that error using Clickz Latest? I've seen some possibilities involving |
@glowkeeper This got fixed with #3112 and will be released with 1.2.2. |
Awesome! When is 1.2.2 due for release? |
@nivida When is 1.2.2 due for release ?) |
@nivida - I appreciate you're probably busy, but I'm trying to work out project plans for some of my dApps, and that 1.2.2 upgrade has become an important ingredient of those plans. Any news on release dates? |
The release is planned for Monday. I will do the last tests and improvements over the weekend and will release it in the late afternoon on Monday (CEST) |
Brilliant - thanks, @nivida |
Problems? |
Oooo - just seen the new version - awesome - thanks @nivida! |
The latest change in httpprovider breaks CORS with ganache and possibly other tools (for me at least), where the CORS-domain cannot be set explicitly.
Chrome comes up with the following error message: "Failed to load http://localhost:7545/: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. Origin 'null' is therefore not allowed access. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute."
Reproduce this issue by using the web3 0.20, e.g. "npm install [email protected]" and then a simple index.html with the most simplistic content opening in Chrome:
Anything I can do on my side?
https://github.com/ethereum/web3.js/blob/b4c1542ddb5284267f6814ba0106bfbbc83fe166/lib/web3/httpprovider.js#L66
The text was updated successfully, but these errors were encountered: