Check for blacklist wildcards before creating GURL
The policy blacklist parser used to first check for "file" schemes first as a special case before checking for wildcard hosts like "http://*", and the file special-case had it's own wildcard special casing. I am working on making "*" an invalid host character, and with this future patch, creating a GURL of "file://*" will fail. This change moves the wildcard handling above the file scheme checking so it will work regardless of whether "*" is a valid host character or not. The particular structure of this code looks like a result of adding the wildcard handling ( https://codereview.chromium.org/1692503002/ ) after the file handling was already in place. BUG=652808 Review-Url: https://chromiumcodereview.appspot.com/2426733002 Cr-Commit-Position: refs/heads/master@{#426532}
Showing
Please register or sign in to comment