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
Wildcards are not restricted to appear only in the leftmost position, but they must wildcard an entire label. (I.e. ..foo is a valid rule: *bar.foo is not.)
...but the parsing code only looks for a single wildcard in the leftmost position:
We used to support wildcards in any position but following up on this discussion on the official project: publicsuffix/list#145 (comment) it appears that the current agreement is to only support wildcards at the last position (and official documentation is yet to be updated with this change). Ultimately, this also allows for more efficient matching. It would be pretty easy to support it again though, but it does not seem like it's happening for now.
The PSL's spec says:
...but the parsing code only looks for a single wildcard in the leftmost position:
tldts/bin/parser.js
Line 32 in e7c140c
There aren't actually any present rules that have a non-leftmost wildcard, so this is a future-proofing concern.
The text was updated successfully, but these errors were encountered: