CSP: source-expression like "foo.bar" doesn't match "http://.foo.bar" |
||||
Issue descriptionThere is possibly a problem when an url with an empty sub-host is checked against CSP. It's maybe not a big deal, as we apparently transparently rewrite `.example.com` to `example.com` for navigations. With url = "http://.example.com", the current behavior is: * If source-expression = "*.example.com" => allow * If source-expression = "example.com" => block. Maybe the current behavior is the correct one. We need to think about it. There is a test that documents this behavior: https://codereview.chromium.org/2697853002/
,
Feb 21 2017
Interesting, will CSP module implement a general high-perf host match engine in C++? I know AdBlock use (like bloom filter) to consolidate the matching performance. If CSP enhance this feature, i thought it can be used to block subresource requests...
,
Feb 23 2017
,
Nov 10 2017
,
Feb 18 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, Feb 15 2017