Closed
Bug 1799166
Opened 2 years ago
Closed 1 year ago
Early Hints: Parse additional header fields for referrer-policy
Categories
(Core :: Networking: HTTP, task, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
109 Branch
Tracking | Status | |
---|---|---|
firefox109 | --- | fixed |
People
(Reporter: acreskey, Assigned: acreskey)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
When the server responds with a referrer-policy header, we should respect it and restrict the outgoing requests accordingly.
Currently only the referrerpolicy passed in the Link header directly is parsed (e.g. via Link: <style.css>; rel=preload; as=style; referrerpolicy=no-referrer).
Assignee | ||
Comment 1•2 years ago
|
||
The early hint may have two referrer policies, one from the response header and one from the link element.
The link header referrer priority, if present, will take precedence over the response referrer policy.
Assignee | ||
Comment 2•2 years ago
|
||
We have a web platform test that makes use of the referrer-policy in the server response here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1758698
Updated•1 year ago
|
Attachment #9302585 -
Attachment description: *wip* Bug 1799166 - Early Hints: Parse additional header fields for referrer-policy → Bug 1799166 - Early Hints: Parse additional header fields for referrer-policy r=#necko-reviewers,ckerschb!
Updated•1 year ago
|
Attachment #9302585 -
Attachment description: Bug 1799166 - Early Hints: Parse additional header fields for referrer-policy r=#necko-reviewers,ckerschb! → Bug 1799166 - Early Hints: Parse additional header fields for referrer-policy r=#necko-reviewers,ckerschb!,manuel!
Pushed by acreskey@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/74ecf8abe97a Early Hints: Parse additional header fields for referrer-policy r=ckerschb,manuel
Comment 4•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox109:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•