URL Blacklist policy gets a confused by a hashtag symbol
Reported by
ad...@cvalka.info,
Mar 10 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Set the policy "URLBlacklist" to "example.com/#/path1/" 2. In Chrome go to "example.com/path2/" 3. Get ERR_BLOCKED_BY_ADMINISTRATOR What is the expected behavior? "example.com/path2/" should not match "example.com/#/path1/" What went wrong? "example.com/path2/" was matched by "example.com/#/path1/" Did this work before? No Chrome version: 56.0.2924.87 Channel: n/a OS Version: OS X 10.10.5
,
Mar 10 2017
Reproduced on Chrome OS.
,
Mar 10 2017
The reason it happens, is the # is the reference separator in an URL. The URLBlackList policy ignores the reference, according to: https://www.chromium.org/administrators/url-blacklist-filter-format As a result, it considers the filter as being everything prior to the reference, which means the whole example.com domain gets blocked. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Mar 10 2017