Problem with "\h"

[sidki3003]

ProxRocks Wrote:Is that going to be included in the next release?

Yep

z12 Wrote:It seems that no matter how you cut it, "\h" can't be used reliably with country codes.

\h has two functions: to store the hostname and to serve as a domain test.
The first function always works, eg: Match = "*" Replace = "\h" .
The second function fails on 2-level TLDs, eg: Match = "://(^\h)" .

If you store the hostname like "$SET(host=\h)", you are using the first function.
If you are storing the real domain in "dom", the intention is to replace the second \h function with eg:
Match = "://(^([^/]++.|)$TST(dom))"

So here is a test filter, reference site is http://bbc.co.uk/. Result is displayed upper left:

Code:

[Patterns]
Name = "Domain Test"
Active = TRUE
Multi = TRUE
Limit = 1
Match = "(?)\1$STOP()"
"$SET(dref=http://bbc.co.uk/)"
"$SET(dhost=\h)"
""
"$TST(dhost="
"([0-9.]+)\9(^?)"
"|"
"(|*.)"
"("
"[^.]+."
"((com|net|edu|gov|org|mil|info|??).??|[^.]+)"
")\9(^?)"
")"
"$SET(dom=\9)"
""
"($TST(dref=*://([^/]++.|)$TST(dom)*)$SET(2=onsite)|$SET(2=offsite))"
Replace = "<div>\2: \9</div\r\n\1$SET(dref=)$SET(dhost=)"

Siamesecat: For most sites outside the US the country code is the top level domain.


sidki