Closed Bug 1725227 Opened 10 months ago Closed 10 months ago

The partitionKey doesn't honor non-standard port

Categories

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

defect

Tracking

()

RESOLVED INVALID

People

(Reporter: timhuang, Assigned: timhuang)

References

Details

Attachments

(1 obsolete file)

We won't add non-standard port when we construct the partitionKey. This is wrong by definition and we will use incorrect partitioned storage.

Ideally, we should migrate the partitioned storage back to the one with port. However, it's not possible because we don't know which port was used when created the partitionKey. And the change won't have a big impact on our network partitioning protection. However, it will affect partitioned Storage in dFPI, it will look like the partitioned storage for non-standard ports was cleared after we fix this issue. But, we cannot really do anything here. So, we won't do the migration.

Pushed by tihuang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/21a7cf38f15a
Fixing the issue that the port doesn't appear in the partitionKey. r=pbz
Flags: needinfo?(tihuang)

This bug should be invalid. See https://html.spec.whatwg.org/#obtain-a-site

A site consists of scheme and host, but without port. And we only apply port to the host that doesn't have a registrable domain, such as, IP address or Public suffix.

Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Flags: needinfo?(tihuang)
Resolution: --- → INVALID
Attachment #9235852 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.