If no filter ever matches, the default is to allow the request.ĭenies all requests to, and sub.ĭenies all HTTP requests to and any of its subdomains, but allows HTTPS and FTP requests.
If no valid filter is left at this stage, the host is reduced by removing the left-most subdomain, and starting again from step 1.From these filters, the filters with the longest set of query tokens are selected.From these filters, the filters with the longest matching path are selected.Filters with a non-matching scheme or port are discarded. The filters with the longest host match are selected.only matches exactly Filter selection process
(dot) prefixing the host, only exact host matches are filtered. When both a block and allow filter apply at step 4 below, with the same path length and number of query tokens, the allow filter takes precedence.Wildcards ( *) are the last searched, and match all hosts.The filter selected for a URL is the most specific match found. If it is the case, that suffix is ignored. For example, If you include a reference separator #, it is ignored along with everything that appears after it. You can include user:pass fields but they will be ignored.The filters format is very similar to the URL format. The patterns custom:app or custom://app are invalid.The patterns custom://* or custom:* are valid and match custom:app.The scheme and the host are case insensitive, but path and query are case sensitive. Custom schemes are supported, but only the patterns scheme:* and scheme://* are allowed. Supported standard schemes are:Īll other schemes are treated as custom schemes. You can use either a standard or a custom scheme. A query token can optionally end with * to indicate prefix match. Must be a valid port value from 1 to 65535.Ī set of key-value and key-only tokens delimited by &. (dot) can prefix the host field to disable subdomain matching. For details, see Schemes you can use.Ī valid hostname or an IP address. This field is optional, and must be followed by ://.
0 kommentar(er)
