Open
Bug 1408263
Opened 7 years ago
Updated 2 years ago
Check referrer policy from meta tag is high priority than referrer-policy header
Categories
(Core :: DOM: Security, enhancement, P3)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: tnguyen, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog1])
Attachments
(1 file)
We expect the order in [1] but currently, we only have tests on meta referrer and noreferrer (and a few referrerpolicy attr)
Firstly we may have to add Referrer-Policy header and referrerpolicy attr order test, then fix if there's any issue.
[1] https://html.spec.whatwg.org/multipage/urls-and-fetching.html#referrer-policy-attribute
|
Reporter | |
Updated•7 years ago
|
Priority: -- → P3
|
||
Updated•7 years ago
|
Whiteboard: [domsecurity-backlog1]
|
|
Reporter | |
Updated•6 years ago
|
Blocks: refactor-referrer-policy-setup
|
|
Reporter | |
Comment 1•5 years ago
|
||
We have all tests to make sure the correct order, except Referrer-policy header
|
|
Reporter | |
Updated•5 years ago
|
Summary: Check order of referrer policy using in request if there are multiple types of Referrer Policy delivery → Check referrer policy from attr is high priority than referrer-policy header
|
|
Reporter | |
Updated•5 years ago
|
Summary: Check referrer policy from attr is high priority than referrer-policy header → Check referrer policy from meta tag is high priority than referrer-policy header
|
|
Reporter | |
Comment 2•5 years ago
|
||
|
|
Reporter | |
Comment 3•5 years ago
|
||
The generate.py is broken, I have just asked in github. I just leave the patch here and come back when I have time.
|
|
Reporter | |
Updated•5 years ago
|
No longer blocks: refactor-referrer-policy-setup
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•