Issue metadata
Sign in to add a comment
|
Refused to get unsafe header “X-Bandwidth-Est 3”
Reported by
lennart....@gmail.com,
Dec 7 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Example URL: https://youtube.com/ Steps to reproduce the problem: 1. Go to YouTube 2. Open Dev Tools (F12) 3. Start playing any video What is the expected behavior? What went wrong? In the dev tools you will see several lines with base.js:6234 Refused to get unsafe header "X-Bandwidth-Est3" Those keep coming and if you are developing a page with the YouTube player you will get many more. It is quite disturbing since it is much harder to find the debug output from your own code. Did this work before? Yes Not sure about the version, but it started with the latest Chrome update today. Chrome version: 63.0.3239.84 Channel: stable OS Version: 10.0 Flash Version: https://stackoverflow.com/questions/47691404/is-there-anyone-who-know-what-refused-to-get-unsafe-header-x-bandwidth-est-3/47693206#47693206
,
Dec 7 2017
This is a bug, not Chrome's, rather should be reported to YouTube app owners. You should be able to introduce a negating console filter that would hide this particular message as a temporary measure.
,
Dec 8 2017
Thanks, looks like you are right. I don't see the bug any more and my version of Chrome is the same. So it looks like they have fixed it at YouTube. (BTW, I have no idea of where to report YouTube bugs. Did someone here report it to YouTube?) |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, Dec 7 2017