New issue
Advanced search Search tips

Issue 916257 link

Starred by 1 user

Issue metadata

Status: Closed
Owner: ----
Closed: Dec 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

URLBlacklist = ['*'] not implicitly whitelisting internal pages

Project Member Reported by timkovich@google.com, Dec 18

Issue description

Chrome OS: 11424.0.0

It was my understanding that setting URLBlacklist to ['*'] should still allow access to certain websites, namely chrome://* and google.com as to not completely hobble the device. As of M-73 this is not the case.

Is this the desired behavior?

Source: https://testtracker.googleplex.com/tc/5727bf4a-1c3c-410c-b8d1-72aced31db2e
 
Description: Show this description
Cc: pmarko@chromium.org emaxx@chromium.org
Maksim, Pavol - this seems more in the realm of enterprise behavior. Who is a good contact for this?
Cc: igorcov@chromium.org
+igorcov@: Igor, I vaguely remember that you did some investigation of this case. Or was that something different?
I did some research[1], and as far as I can see, the policy never worked the way it is described in that manual test case. It only explicitly whitelists:
- chrome-extension
- chrome-native
- chrome-search

[1]: https://cs.chromium.org/chromium/src/components/policy/core/browser/url_blacklist_manager.cc?q=kBypassBlacklistWildcardForSchemes&g=0&l=57 
Status: Closed (was: Untriaged)
I misread this testcase, I'm going to close this bug.

Sign in to add a comment