`Response`s provided by service workers must respect COOP/COEP
Categories
(Core :: DOM: Service Workers, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox78 | --- | fixed |
People
(Reporter: perry, Assigned: edenchuang)
References
Details
Attachments
(2 files, 1 obsolete file)
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Updated•5 years ago
|
|
|
Reporter | |
Comment 1•5 years ago
|
||
Move ProcessCrossOriginResourcePolicyHeader into the base class of
InterceptedHttpChannel and nsHttpChannel, HttpBaseChannel.
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 2•4 years ago
|
||
I am working on it. Take it from Perry.
|
|
Reporter | |
Updated•4 years ago
|
|
|
||
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
||
Comment 3•4 years ago
|
||
The problem here is that responses emitted from service worker do not apply COOP/COEP properly and therefore might not end up being isolated even though they should be.
|
|
Assignee | |
Comment 4•4 years ago
|
||
|
||
Updated•4 years ago
|
|
|
||
Updated•4 years ago
|
|
|
Assignee | |
Comment 5•4 years ago
|
||
This bug is for supporting COEP, CORP, and COOP checking on the response from SW.
nsHttpChannel::ProcessCrossOriginEmbedderPolicy(), nsHttpChannel::ProcessCrossOriginResourcePolicy() and nsHttpChannel::ComputeCrossOriginOpenerPolicyMismatch() should be also applied on InterceptedHttpChannel, such that response from SW could be applied with COEP, CORP, COOP checking.
When the response with COOP mismatch, that means the loading needs to be performed in the other process.
Currently, DocumentLoadListener determines if the loading should be switched to another process in MaybeTriggerProcessSwitching(), and nsHttpChannel::HasCrossOriginOpenerPolicyMismatch() is used for COOP mismatch switching. That means there would be at least two things need to do
- InterceptedHttpChannel needs also to provide HasCrossOriginOpenerPolicyMismatch() which likes nsHttpChannel did.
- DocumentLoadListener only works with nsHttpChannel, it needs to be supported with InterceptedHttpChannel.
|
|
Assignee | |
Comment 6•4 years ago
|
||
Pushed by dluca@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/bb01a66dd630 P1 Move CrossOriginXXXHeaders checking into HttpBaseChannel and apply CrossOriginXXXHeaders in InterceptedHttpChannel. r=valentin https://hg.mozilla.org/integration/autoland/rev/bf67f9734e0d P2 Apply COOP switch with InterceptedHttpChannel in DocumentLoadListener r=necko-reviewers,valentin,mattwoodrow
|
||
Comment 8•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/bb01a66dd630
https://hg.mozilla.org/mozilla-central/rev/bf67f9734e0d
Description
•