ForceYouTubeSafetyMode not consistently following expected behavior
Reported by
stepheng...@amplifiedit.com,
Mar 18 2016
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 7647.84.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce the problem: 1. in an Unmananaged Chrome browser, goto youtube.com and sign in using a managed user with ForceYouTubeSafetyMode = true (Cloud Policy) - observe Restricted Mode setting @ bottom of page (off) 2. Login to ChromeBrowser using the same account - observe Restriced Mode setting @ bottom of page (off - expected on) 3. Clear the browser's Cache, and observe Restricted Mode Setting (on) 4. Sign back into YouTube - observe Restriced Mode setting (off - expected on) What is the expected behavior? Whenever the Cloud Policy is present, it should override the previous setting. What went wrong? In steps 2 and 4, when a ChromeProfile policy should be forcing Restricted Mode, somewhere they are pulling the previous setting which is by default Off. Did this work before? N/A Chrome version: 48.0.2564.116 Channel: stable OS Version: 7647.84.0 Flash Version: Shockwave Flash 20.0 r0
,
Mar 29 2016
Marc, could you please take a look? Feel free to assign the bug back to me if you are not the right owner for this. And, I guess, the ForceGoogleSafeSearch policy may also have the same issue.
,
Mar 29 2016
My testing on SafeSearch was that it was working as intended. It appends a query on the URL which forces the state of SS to on. There is no such query within Youtube appended to the URL, from an End User PoV.
,
Mar 29 2016
,
Mar 29 2016
The YouTube policy uses an HTTP header rather than a URL param, so it's not easily visible to the user. But if the SafeSearch policy works, then I'm confident that the YouTube one works too. From the description, it looks to me like YouTube doesn't use the header if you're signed in to YouTube. Could you try this again, but in step 3, instead of clearing the cache, just sign out of YouTube?
,
Apr 13 2016
,
Apr 18 2016
Here's another report of the same (or along the same vein): https://plus.google.com/u/0/103198181016995207918/posts/f43MSTBJHnU See the paragraph of "The teacher found a work around..." I will attempt to reproduce without clearing cache, but even the clearing of the cache shouldn't break the process, and if it does, should be addressed.
,
Apr 19 2016
My theory is that clearing the cache is not actually related, but it's rather signing in/out of YouTube that makes a difference. Either way, agreed, this should be addressed. I'm just trying to narrow down the cause. Thanks for your help in tracking this down!
,
Nov 10 2016
,
Nov 15 2017
,
Nov 17 2017
,
Dec 15 2017
The ForceYouTubeSafetyMode policy has been deprecated in favor of the ForceYouTubeRestrict policy. Please reopen the bug or file a new one if the new policy suffers from a similar issue. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by scunning...@chromium.org
, Mar 21 2016