Open
Bug 1944556
Opened 1 month ago
Updated 23 days ago
Implement PNA detection in Necko
Categories
(Core :: Networking: HTTP, enhancement, P2)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: smayya, Assigned: smayya)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(6 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
This bug will implement detection of Private Network Access for a Request.
Specifically, we will implement the following for PNA:
- Part 1 Private Network Access is detected in transaction/connection manager and error if :
- Preflight is not done for this request AND
- the request is not a CORS-PNA preflight request AND
- the target address space is less private compared to the triggering principal's address space.
- Part 2 The error is propagated by failing the transaction through call backs in OnStartRequest
- Part 3 A flag to indicate if preflight is successful. This will be used by the transaction/connection manager.
Assignee | ||
Updated•1 month ago
|
Assignee: nobody → smayya
Assignee | ||
Comment 1•1 month ago
|
||
Assignee | ||
Comment 2•23 days ago
|
||
Assignee | ||
Comment 3•23 days ago
|
||
Assignee | ||
Comment 4•23 days ago
|
||
Assignee | ||
Comment 5•23 days ago
|
||
Assignee | ||
Comment 6•23 days ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•