1639154 - Isolate network cache per first-party when privacy.partition.network_state is set to true

Status: RESOLVED FIXED

(Core :: Privacy: Anti-Tracking, task)

Comment 1

[Andrea Marchesini [:baku]]

Attachment: Bug 1639154 - Isolate network cache per first-party when privacy.partition.network_state is set to true - part 1 - implementation, r?mayhemer

Comment 2

[Andrea Marchesini [:baku]]

Attachment: Bug 1639154 - Isolate network cache per first-party when privacy.partition.network_state is set to true - part 2 - tests, r?mayhemer

Depends on D75921

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/66abd66fc467
Isolate network cache per first-party when privacy.partition.network_state is set to true - part 1 - implementation, r=mayhemer,necko-reviewers
https://hg.mozilla.org/integration/autoland/rev/7e53b5398797
Isolate network cache per first-party when privacy.partition.network_state is set to true - part 2 - tests, r=mayhemer

Comment 4

[Thorin [:thorin]]

Excuse my ignorance, but with these patches, such as this one and Bug 1639247, do they isolate the "same" as FPI (privacy.firstparty.isolate) or is it different? (note: FPI & dFPI in Bug 1631676). In other words, when flipped on, will they causes any conflicts or always be the most restrictive if there is a difference in approach? TIA

Comment 5

[Bogdan Tara[:bogdan_tara | bogdant]]

https://hg.mozilla.org/mozilla-central/rev/66abd66fc467
https://hg.mozilla.org/mozilla-central/rev/7e53b5398797