You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While discussing #165 (comment), we agreed that semicolons are allowed by source expression grammar (path-part, in particular. ). However, semicolon is a directive delimiter, and comma is a policy delimiter.
While it is not possible to parse a policy that whitelists a URL containing ; or ,, it should be possible to parse and match percent encoded versions of such URLs. https://w3c.github.io/webappsec-csp/#match-paths covers this part by requiring to percent decode paths before matching.
The text was updated successfully, but these errors were encountered:
shekyan
added a commit
to shekyan/salvation
that referenced
this issue
Jan 1, 2017
While discussing #165 (comment), we agreed that semicolons are allowed by source expression grammar (path-part, in particular. ). However, semicolon is a directive delimiter, and comma is a policy delimiter.
While it is not possible to parse a policy that whitelists a URL containing
;
or,
, it should be possible to parse and match percent encoded versions of such URLs. https://w3c.github.io/webappsec-csp/#match-paths covers this part by requiring to percent decode paths before matching.The text was updated successfully, but these errors were encountered: