Skip to content

rules: fix regex for matching any TLD #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RavuAlHemio wants to merge 1 commit into
base: master
Choose a base branch
from
Open

rules: fix regex for matching any TLD #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/specs/rules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ The typical structure is `<protocol><subdomain><domain name><TLD><directorie>?<f

In most cases the following expression covers all the needs, you only have to substitute the remaining `<>`
fields: `^https?://(?:[a-z0-9-]+\\.)*?<domain name>\\.<TLD>`. If you want to match with every TLD,
you can substitute the TLD field with `(?:[a-z]{2,}){1,}`.
you can substitute `\\.<TLD>` with `(?:\\.[a-z]{2,}){1,}`.

### `completeProvider`
The **completeProvider** is a boolean, that determines if every URL that matches the **urlPattern** will be blocked.
Expand Down