Issue metadata
Sign in to add a comment
|
Chrome doesn't allow 'same-origin' as Referrer-Policy header value
Reported by
pelikans...@gmail.com,
Apr 15 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Linux; Android 7.0; SAMSUNG SM-G930F Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/5.0 Chrome/51.0.2704.106 Mobile Safari/537.36 Steps to reproduce the problem: 1. Visit http://smares.de/ 2. Open the developer console What is the expected behavior? No errors should appear 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? N/A Chrome version: 57 Channel: stable OS Version: Flash Version: See https://support.google.com/chrome/forum/AAAAP1KN0B0UBp_FtxonXU/?hl=en
,
Apr 19 2017
[estark]: You hooked up the referrer policy logic in net/, are you familiar with it in content, too?
,
Apr 19 2017
Erm, in blink, too, rather
,
Apr 19 2017
Hope so!
,
Apr 19 2017
Chrome doesn't yet support same-origin, strict-origin, or strict-origin-when-cross-origin, but hopefully will soon! Planning on implementing them this quarter. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Apr 17 2017