Issue metadata
Sign in to add a comment
|
Add support for more referrer policies
Reported by
goo...@leonklingele.de,
Apr 10 2017
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36
Steps to reproduce the problem:
Chrom{e,ium} currently only supported these five referrer policies:
- no-referrer
- no-referrer-when-downgrade
- origin
- origin-when-cross-origin
- unsafe-url
Please add support for the remaining three found at https://www.w3.org/TR/referrer-policy/#referrer-policies
- same-origin
- strict-origin
- strict-origin-when-cross-origin
- (empty string)
Especially the first one (same-origin) is important IMO.
What is the expected behavior?
What went wrong?
Failed to set referrer policy: The value 'same-origin' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origin-when-cross-origin', or 'unsafe-url'. The referrer policy has been left unchanged.
Did this work before? No
Chrome version: 57.0.2987.133 Channel: n/a
OS Version:
Flash Version:
,
Jul 18 2017
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by est...@chromium.org
, Apr 10 2017Status: Duplicate (was: Unconfirmed)