Open Bug 1502573 Opened 6 years ago Updated 2 years ago

Tracking Protection doesn't prevent connection to tracking service

Categories

(Core :: Privacy: Anti-Tracking, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox65 --- affected
firefox66 --- affected

People

(Reporter: jan, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: nightly-community, ux-trust)

Attachments

(1 file)

Debian Testing

STR:
mozregression --launch 2018-10-26 --pref network.warnOnAboutNetworking:false security.OCSP.enabled:0 network.captive-portal-service.enabled:false browser.search.geoip.url:'' browser.aboutHomeSnippets.updateUrl:'' browser.search.geoSpecificDefaults.url:'' network.dns.disablePrefetch:true network.prefetch-next:false network.http.speculative-parallel-limit:0 privacy.trackingprotection.enabled:true -a https://bugzilla.mozilla.org/show_bug.cgi?id=1496662 -a about:networking

Actual: There is a connection to Google Analytics.

Expected: No connection as the request log says:
> The resource at “https://www.google-analytics.com/analytics.js” was blocked because content blocking is enabled.[Learn More]
I noticed this problem in my main profile despite having uBlock Origin.
Did you visit a website owned by Google (e.g. Youtube or Google Search)?

We don't block google-analytics.com on Google's properties because we consider that first-party tracking in that case.

On the other hand, if you see google-analytics being loaded on a non-Google site, then that would be a bug.
Flags: needinfo?(jan)
I ran https://mozilla.github.io/mozregression/install.html with above command. It opened BMO. Then I switched to the about:networking tab and made screenshots. It doesn't happen if I only load about:networking.
Flags: needinfo?(jan)
So what you're saying is that if we visit bugzilla.mozilla.org in a new profile with TP enabled, then bugzilla still manages to load Google Analytics?

Was bugzilla.mozilla.org the only URL that was loaded in that run?
Flags: needinfo?(jan)
> So what you're saying is that if we visit bugzilla.mozilla.org in a new profile with TP enabled, then bugzilla still manages to load Google Analytics?

Yes. It looks like there is no succesful request (I don't know) because we get
> The resource at “https://www.google-analytics.com/analytics.js” was blocked because content blocking is enabled.[Learn More]
but a connection was established. As prefetching etc. is disabled, there shouldn't be even a connection.
Flags: needinfo?(jan)
OS: Linux → All
Hardware: x86_64 → Desktop
> Was bugzilla.mozilla.org the only URL that was loaded in that run?

Yes. Please just run the command from comment 0.
Ok thanks for the extra details.

Let's see if that's still the case once bug 1207775 is fixed.
Depends on: 1207775
Priority: -- → P3
Still reproducible.

mozregression --launch 2018-12-23 --pref network.warnOnAboutNetworking:false security.OCSP.enabled:0 network.captive-portal-service.enabled:false browser.search.geoip.url:'' browser.aboutHomeSnippets.updateUrl:'' browser.search.geoSpecificDefaults.url:'' network.dns.disablePrefetch:true network.prefetch-next:false network.http.speculative-parallel-limit:0 privacy.trackingprotection.enabled:true -a https://bugzilla.mozilla.org/show_bug.cgi?id=1496662 -a about:networking

When bug 1515144 gets deployed we need to use a different test website.
To be clear, the likely fix for this is bug 1207775.
Component: Protections UI → Privacy: Anti-Tracking
Product: Firefox → Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: