1970228 - Partitioning should begin at a scheme change

Status: NEW

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

Description

[Benjamin VanderSloot [:bvandersloot]]

Our calculation of when something is "third party" doesn't include the scheme. But our partition keys do. This leads to a weird case where a secure-same-base-domain iframe inside of an insecure top level is not partitioned when it is in every other browser. I think this probably causes some WPT failures.

Here is a try of a rough cut of it.

https://treeherder.mozilla.org/jobs?repo=try&revision=da88ddaa6f071b59d750adda0186e60d0a189a75

See https://github.com/privacycg/storage-partitioning/issues/50 for discussion.

We don't want to accidentally make cookies schemeful at the same time though, so let's be careful.

Third partiness should probably be computed inside of the principal, rather than in a weird service hanging out.

Comment 1

[Leo Liu [:leoliu]]

Attachment: WIP: Bug 1970228 - Partitioning should include scheme r?bvandersloot!