-
-
Notifications
You must be signed in to change notification settings - Fork 381
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
Yellowlist api.infura.io #1966
Comments
Why is the domain getting blocked in the first place though? Could you run the following script in your Badger's background page console and share what it prints out? (function () {
const STR = "infura.io";
console.log("**** ACTION_MAP for", STR);
_.each(badger.storage.getBadgerStorageObject('action_map').getItemClones(), (obj, domain) => {
if (domain.indexOf(STR) != -1) console.log(domain, JSON.stringify(obj, null, 2));
});
console.log("**** SNITCH_MAP for", STR);
_.each(badger.storage.getBadgerStorageObject('snitch_map').getItemClones(), (sites, domain) => {
if (domain.indexOf(STR) != -1) console.log(domain, JSON.stringify(sites, null, 2));
});
}()); To get to the background page console in Chrome, visit In Firefox, visit |
|
Is this a case of session cookies (you being signed into the service) being sent along when fetching third-party resources provided by the same service? If this is what it is, then a couple of suggestions:
|
Those sound like suggestions for the operators of Infura (which doesn't include me - I'm just working on sites that call their API). The Is there anything else I can do to help diagnose what's causing it to be blocked. |
Yes, could you please check if your session cookies are being unnecessarily sent along with Infura API requests? If that's the case, we should get in touch with Infura to make the above suggestions. |
You could check by visiting your cookie management screen ( |
Privacy Badger has a habit of redlisting
api.infura.io
, a blockchain-as-a-service API used by some Ethereum distributed applications, breaking the applications. Since the API is stateless, it works quite happily yellowlisted.The text was updated successfully, but these errors were encountered: