Content Security Policy Issue in next js example repo about fingerprintjs HOT 4 CLOSED

@jimsheen thanks for letting us know about this issue, we're going to look into it asap and get back to you!

from fingerprintjs.

Hello @jimsheen, thanks for reaching out!

Is it possible that Adblock, uBlock, or a similar extension in your browser is blocking the requests? Have you tried running the page in a browser without extensions?

Our Next.js example does not contain any CSP headers by default. During my tests, whenever Fingerprint was blocked by CSP, I would get a CSP-specific error in the console such as: Content Security Policy: The page’s settings blocked the loading of a resource at https://fpjscdn.net/v3/2UZgp3skqLzfJpFUGUrw (“default-src”).

On the other hand, requests blocked by ad-blockers often result in a generic ERR_BLOCKED_BY_CLIENT error.

You can side-step ad-blocking extensions by routing the requests through a subdomain on your website or using our Cloudflare integration.

Let us know if an extension was the problem, if not, we will investigate further!

from fingerprintjs.

@jimsheen Please double-check you Chrome extensions. Bare Chrome doesn't block Fingerprint Pro requests. The quickest way to disable all extensions is going into Incognito mode.

from fingerprintjs.

@JuroUhlar Thanks for the swift reply. I was using Brave browser for local development, tried to run the example project in chrome and disabled adblock but still getting the same issue. However, it did work in Firefox so at least I have a way to test the implementation in my local environment.

When it comes to deployment I will look into routing through a sub domain as you mentioned - many thanks for the helpful reply and links!

from fingerprintjs.