I am not entirely sure if this is a bug or intented behaviour, but Behave! detects sites accessing resources from IPFS when using a local gateway (IPFS Desktop and IPFS Companion) and I think there should possibly be an option to whitelist it as it's the expected behaviour of IPFS Companion.
Select IPFS Companion from browser toolbar and click on "Go To My Node" and Behave! will warn about access to 127.0.0.1:5001 (IPFS default API port).
Alternatively visit a webiste such as mine, https://mikaela.info/, which fetches resources (in my case my avatar and favicon) from IPFS and Behave! warns about mikaela.info accessing 127.0.0.1:8080 (default IPFS Gateway port).
when the user isn't using IPFS Companion and IPFS Desktop/daemon, the site currently makes requests to ipfs.dweb.link instead. The purpose of IPFS Companion is to redirect the request to local gateway instead of a public one.
Since I opened this issue, I have also started trying IPFS CDN which is a fork of Decentraleyes that currently redirects Jquery requests to local IPFS gateway and also causes notifications.
I am not entirely sure if this is a bug or intented behaviour, but Behave! detects sites accessing resources from IPFS when using a local gateway (IPFS Desktop and IPFS Companion) and I think there should possibly be an option to whitelist it as it's the expected behaviour of IPFS Companion.
Example steps:
127.0.0.1:8080
(default IPFS Gateway port).ipfs.dweb.link
instead. The purpose of IPFS Companion is to redirect the request to local gateway instead of a public one.