UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2652.0 Safari/537.36

Example URL:

Steps to reproduce the problem:
CSP level 2 specification describes how source-expressions containing non-empty path-part in section 4.2.2.11 https://www.w3.org/TR/CSP2/#match-source-expression, which implies that no matter if `exact-match` is true or not,  matching of path-list entries should be performed in case-insensitive way.
Aboce is valid for CSP level 3 as well.

What is the expected behavior?
Perform path-part matching according to the specification.

exact-match: true
content-security-policy: script-src example.com/script.js
resource at: example.com/Script.js
result: doesn't match
expected: should load

exact-match: false
content-security-policy: script-src example.com/A/script.js
resource at: example.com/A/script.js
result: doesn't match
expected: should match

What went wrong?
I expect Chromium to follow the specification or, (more reasonable in this case, as FF implements the same behavior)  update the spec.

Did this work before? N/A 

Chrome version: 50.0.2652.0  Channel: n/a
OS Version: OS X 10.11.3
Flash Version: Shockwave Flash 21.0 r0