23
edits
Gecko:Effective TLD Service: Difference between revisions
→Interpretation
m (added effective tld list link) |
|||
| Line 48: | Line 48: | ||
* Hostnames are also normalized according to RFC 3454 before they are matched against the rules. Thus, among other things, the matching is not case-sensitive. | * Hostnames are also normalized according to RFC 3454 before they are matched against the rules. Thus, among other things, the matching is not case-sensitive. | ||
* If a hostname matches one or more exception rules, the ''shortest'' matching exception will be used. | * If a hostname matches one or more exception rules, the ''shortest'' matching exception (the one with the fewest levels) will be used. | ||
* If a hostname matches more than one non-exception rule in the file, the ''longest'' matching rule (the one with the most levels) will generally be used, unless an exception rule also matches. | * If a hostname matches more than one non-exception rule in the file, the ''longest'' matching rule (the one with the most levels) will generally be used, unless an exception rule also matches. | ||
* However, a shorter rule that contains no wildcards will be used in preference to a longer wildcard rule, and a rule that falls back to a wildcard match at a higher level (closer to the beginning of the name) will be used in preference to one that uses a wildcard at a lower level. | * However, a shorter rule that contains no wildcards will be used in preference to a longer wildcard rule, and a rule that falls back to a wildcard match at a higher level (closer to the beginning of the name) will be used in preference to one that uses a wildcard at a lower level. | ||