Closed Bug 1670617 Opened 7 months ago Closed 6 months ago

Partition the CORS-preflight cache

Categories

(Core :: DOM: Networking, task, P2)

task

Tracking

()

RESOLVED FIXED
84 Branch
Tracking Status
firefox84 --- fixed

People

(Reporter: annevk, Assigned: timhuang)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged], [wptsync upstream])

Attachments

(3 files)

The CORS-preflight cache also needs to be partitioned.

Assignee: nobody → tihuang
Status: NEW → ASSIGNED

We want to partition the CORS preflight cache by the network state
partitioning. So, we have done two things in the patch. First, we make
the CORS preflight cache to be aware of the OriginAttributes. Second, we
use the originAttributes of the network state partitioning in the CORS
preflight cache. As the result, the CORS preflight cache will be
partitioned by the originAttributes.partitionKey as well as other
originAttributes fields if present.

Depends on D93682

Severity: -- → S3
Type: defect → task
Priority: -- → P2
Whiteboard: [necko-triaged]
Pushed by tihuang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/54c86d5c6b74
Part 1: Add a test to verify if the preflight cache is partitioned. r=ckerschb
https://hg.mozilla.org/integration/autoland/rev/df105850ab32
Part 2: Make the CORS preflight cache partitioned by the originAttributes. r=ckerschb,necko-reviewers
https://hg.mozilla.org/integration/autoland/rev/a41982f2e7ff
Part 3: Add a web-platform test for the cors preflight partitioning. r=ckerschb,annevk
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/26287 for changes under testing/web-platform/tests
Whiteboard: [necko-triaged] → [necko-triaged], [wptsync upstream]
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.