WTF: Blocked URL: https://o827986.ingest.sentry.io/api/5818829/envelope/?sentry_key=dfc9b7af16364687a712017b52545d52&sentry_version=7 even though my policy allows it: ...; connect-src ... https://*.ingest.sentry.io ...; In ~6 months there were ~24k users and ~900k views, the issue was reported 47 times. Happens on Firefox v126 and v127, Chrome v125 and v126, Edge v125 and v126. One from IPv4 Cisco OpenDNS, all others coming from 2001:DB8::/32 range, which is a reserved prefix for use in documentation. Upon inspection of user emails, looks like all users from that IP range are from the same company that is our client.
Also have a very similar issue with hotjar, but that one has much more "real" IPv4s, apart from "2001:db8" ones. I'll add more info on that one later, probably in separate PR if this one will get merged by that time.
Added:
connect-src violation for sentry.io, even though allowed
Event from
window.addEventListener("securitypolicyviolation", ...)
:WTF: Blocked URL:
https://o827986.ingest.sentry.io/api/5818829/envelope/?sentry_key=dfc9b7af16364687a712017b52545d52&sentry_version=7
even though my policy allows it:...; connect-src ... https://*.ingest.sentry.io ...
; In ~6 months there were ~24k users and ~900k views, the issue was reported 47 times. Happens on Firefox v126 and v127, Chrome v125 and v126, Edge v125 and v126. One from IPv4 Cisco OpenDNS, all others coming from2001:DB8::/32
range, which is a reserved prefix for use in documentation. Upon inspection of user emails, looks like all users from that IP range are from the same company that is our client.Also have a very similar issue with hotjar, but that one has much more "real" IPv4s, apart from "2001:db8" ones. I'll add more info on that one later, probably in separate PR if this one will get merged by that time.