Open
Bug 1400842
(refactor-referrer-policy-setup)
Opened 7 years ago
Updated 2 years ago
[meta] Refactor Referrer Policy setup
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: ckerschb, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [domsecurity-meta])
At the moment we pass a referrerURI as well as a referrer-policy between frontend and backend. Code for figuring out what referrer to actually send with a request is duplicated.
It would be nice to encapsulate all of that information into a class which you then can ask question like:
* what is the full referrer?
* what referrer should I send with that request (based on the policy)
All of that could then happen in an 'security by default' like style to guarantee we have the same referrer premises for all of the loads.
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [domsecurity-backlog1]
Comment 1•7 years ago
|
||
Thomas had a lot of experience working on Referrer Policy.
He might be able to help this.
Updated•7 years ago
|
Assignee: nobody → tnguyen
Updated•7 years ago
|
Summary: Refactor Referrer Policy setup → [meta] Refactor Referrer Policy setup
Whiteboard: [domsecurity-backlog1] → [domsecurity-meta]
Updated•7 years ago
|
Assignee: tnguyen → nobody
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Alias: refactor-referrer-policy-setup
Reporter | ||
Updated•6 years ago
|
Assignee: nobody → tnguyen
Status: NEW → ASSIGNED
Type: enhancement → task
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Assignee: tnguyen → nobody
Status: ASSIGNED → NEW
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•